Re: static and forward declaration
CodeWarrior is correct in its message. The variables are being defined the first time for use in the procedural_db_register() calls and then later they are defined again but this time with initial values. Does CodeWarrior issue the redefinition message as a warning or as an error? The output from 'gcc -v' on my machine is: Reading specs from /usr/lib/gcc-lib/i386-redhat-linux/egcs-2.91.66/specs gcc version egcs-2.91.66 19990314/Linux (egcs-1.1.2 release) Even though -Wall is specified, gcc accepts it without even a warning. I don't know offhand if this behaviour is allowed by the standard. My personal coding style would put the declaration with initial values before the first use which would eliminate the two lines at the top of the file.
Re: static and forward declaration
Hi, Even though -Wall is specified, gcc accepts it without even a warning. I don't know offhand if this behaviour is allowed by the standard. My personal coding style would put the declaration with initial values before the first use which would eliminate the two lines at the top of the file. I agree. But I will have to do this myself in all the *_cmds.c files. :-( Since all the *_cmds.c files are autogenerated I suspect a very small change to the code-generator would be sufficient. Yosh? Salut, Sven