Re: extraneous warning with gcc & modules

[Bruno H. <br...@cl...>]

Sam wrote:
> is there a way to avoid this warning?
> 
> g++   -W -Wswitch -Wcomment -Wpointer-arith -Wimplicit -Wreturn-type  -Wno-sign-
> compare -Wno-invalid-offsetof -falign-functions=4 -g -DDEBUG_OS_ERROR -DDEBUG_SP
> VW -DDEBUG_BYTECODE -DSAFETY=3 -DDEBUG_GCSAFETY -DHEAPCODES -DUNICODE -DDYNAMIC_
> FFI -I. -I.. -c bdb.m.c -o bdb.o
> In file included from bdb.c:8:
> ../clisp.h:361:1: warning: "HEAPCODES" redefined
> <command line>:7:1: warning: this is the location of the previous definition

Yes: you could avoid it by changing clisp.h to contain
  #define HEAPCODES 1
instead of
  #define HEAPCODES /*empty*/

You know that gcc doesn't warn if the redefinition of a macro has the same
body as the original definition.

Bruno