Recent changes to patches

#32 Do not add space when using cmt_cpp_to_c

2016-04-07T16:56:05.635000Z

status: accepted --> closed

#32 Do not add space when using cmt_cpp_to_c

2016-04-07T16:55:29.197000Z

status: open --> accepted
Group: --> Next Release

#7 ./configure can create debuggable/profile-able binaries

2016-04-07T16:37:52.688000Z

status: open --> closed
Group: --> Next Release

#33 Add before/after options for ternary operators

2013-07-13T17:18:02.125000Z

status: open --> closed
assigned_to: Ben Gardner

Add before/after options for ternary operators

2013-06-09T01:48:53.561000Z

A common format for ternary operators is as follows:

a = b? 1: 0;

i.e. different spacing before and after the '?' and ':'.

This patch adds the options sp_cond_before_colon/sp_cond_after_colon and sp_cond_before_question/sp_cond_after_question which can be used to override sp_cond_colon/sp_cond_question respectively.

Add before/after options for ternary operators

2013-06-09T01:48:53.561000Z

Ticket 33 has been modified: Add before/after options for ternary operators
Edited By: Ben Gardner (bengardner)
Status updated: u'open' => u'closed'
Owner updated: None => u'bengardner'

Do not add space when using cmt_cpp_to_c

2012-03-23T14:46:31Z

When converting CPP comments to C uncrustify adds a space at the beginning of the C comment, eg: //\! test becomes: /\* \! test This breaks doxygen singleline comments that expect the \! to be right after the comment star. this patch changes this behavior and gives the following output: //\! test becomes: /\*\! test I haven't spent much time in the uncrustify code, so please let me know if this is the completely wrong way of doing this.

Do not add space when using cmt_cpp_to_c

2012-03-23T14:46:31Z

Ticket 32 has been modified: Do not add space when using cmt_cpp_to_c
Edited By: Guy Maurel (guymaurel)
Status updated: u'accepted' => u'closed'

Do not add space when using cmt_cpp_to_c

2012-03-23T14:46:31Z

Ticket 32 has been modified: Do not add space when using cmt_cpp_to_c
Edited By: Guy Maurel (guymaurel)
Status updated: u'open' => u'accepted'
_milestone updated: '' => u'Next Release'

handle a backslash followed by a literal newline

2011-10-02T11:10:46Z

Without this change, uncrustify's lexer would get confused for any C code containing a string like this: f \("\ Some text\n"\); That led to a diagnostic like "Garbage in col 8: 5c" typically followed by a cascade of unwarranted diagnostics. The fix is to reset "escaped" also when handling a literal newline or a carriage return. Also included: a test case to exercise the bug/fix: tests/c.test tests/input/c/backslash-newline-lex.c tests/output/c/01060-backslash-newline-lex.c