Wireshark · Ethereal-dev: RE: [Ethereal-dev] Conversion of @foo@ macros in config.h.win32

["Bryan Miller" <millerb@xxxxxxx>]

Guy Harris appears to have written:

I guess I walked right into that one :-)

[snippy-snip] 

> To quote the comment in config.nmake:
> 
>     # Nmake uses carets to escape special characters
> 
> and to quote the nmake documentation at
> 
>
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/vcug98/
html/_asug_special_characters_in_macros.asp
>
> "A number sign (#) after a definition specifies a comment. To specify
a
> literal number sign in a macro, use a caret (^), as in ^#."

Only 6 of the 55 #defines in config.h are "escaped" with the caret token
and the remaining 49 work fine with nmake.  What, if anything is special
about
those six?  Usually, I see the caret token used in makefiles and not in
header
files, hence my question.

> Then perhaps Opus make isn't compatible with nmake - in which case it
shouldn't
> be used with Makefile.nmake, as Makefile.nmake is written for use with
nmake and
> expects nmake semantics.

Opus make with the /EN switch is meant to be nmake compatible and it
allows
me to use winkins in ClearCase where nmake doesn't.  It isn't essential
but
with the plug-ins I am developing it reduces my compile times
substantially.

I will try running nmake without the caret (^) and see what happens.

Cheers