On Fri, Aug 31, 2018 at 12:57:14PM +1000, Jonathan Gray wrote:
> update tradcpp to 0.5.2
> 
> release 0.5.2 (20160904)
>    - Fix typo in -U usage message, noticed by Joerg.
>    - Add a -debuglog option to send an execution trace to a file.
>      Intended to be used when debugging imake templates and other
>      complex input, not for debugging tradcpp itself.
> 
> release 0.5.1 (20150612)
>    - Fix a stupid regression in 0.5 that causes it to not recognize a
>      pile of options.
>    - Fix output corruption caused by mishandling which macros are
>      currently in use. In particular, "curmacro" is only valid while
>      we're parsing a macro name and arguments, and can change once we
>      start expanding, so don't use it to clear the in-use flag. This
>      problem has been around all along but was only just exposed.
>    - Also don't set curmacro to null after calling expand_domacro as
>      that can cause us to think a macro name we just read is defined().
>      This one was introduced in 0.5.
>    - Don't use "remove" as a local variable as gcc 4.1 gets upset
>      about it vs. remove(3) in stdio.h.
> 
> release 0.5 (20150612)
>    - Don't report unclosed comments as "No newline at end of file".
>    - Don't rely on <stdbool.h> existing, as (predictably) it doesn't
>      work on Solaris.
>    - Similarly, don't rely on C11 anonymous unions as the Solaris
>      compiler vomits on them.
>    - Typo fix in man page from Jason McIntyre; and change "Usage" to
>      "usage" in usage for pedantic reasons, from Igor Sobrado.
>    - Accept "-" as either input or output file name to mean stdin or
>      stdout respectively. Suggested by Jonathan Gray.
>    - Fix output spacing behavior to match gcc when newlines appear in or
>      while looking for macro arguments. Partly from Joerg Sonnenberger.
>    - Implement __FILE__ and __LINE__ macros. Mostly from Joerg Sonnenberger.
>    - Implement #line. Partly from Joerg Sonnenberger.
>    - Declare usage() with PF(). From wiz.

When reading over the patch I noticed a few "unsigned" declarations
which could be expanded to "unsigned int", but some existing decls
already use unsigned so it could be done as a separate patch later.
Overall I think this is worth having even just for __LINE__ & __FILE__,
so it's OK miko@ as is.

Reply via email to