Re: Position of conditionals in ChangeLog

[Alfred M. Szmidt]

   > This looks strnge?  Can the conditional be (or should?) on either side
   > of the function?
   > 
   >    @example
   >    * frame.h [HAVE_X_WINDOWS] (FRAME_WINDOW_P): Macro defined.
   >    @end example
   >    
   >    Next, an entry for a change within the function @code{init_display},
   >    whose definition as a whole is unconditional, but the changes
   >    themselves are contained in a @samp{#ifdef HAVE_LIBNCURSES}
   >    conditional:
   >    
   >    @example
   >    * dispnew.c (init_display) [HAVE_LIBNCURSES]: If X, call tgetent.
   >    @end example

   This looks perfectly logical to me:
     - In the first case, we have a declaration/definition inside #if.
     - In the second case, we have a #if inside a definition.

Where is this "logic" explained in the GCS?  Since it is not how any
of the tools we have at hand work, or differentiate things.  Nor is it
something I've ever heard of before.

And people use either or depending on how they might write things,
with little meaning of where the conditional expression one is
refering to is.

   Is the problem that the Emacs ChangeLog mode does not do good syntax
   highlighting in one of these two cases? If so, it can be fixed in Emacs.

I don't know.  I know that Emacs ChangeLog font-lock is broken when it
comes to these parts of the ChangeLog format.