Article View: gnu.gcc.help
Article #52283GNU CC traditional option
From: wjb4
Date: Wed, 09 Dec 1992 20:09
Date: Wed, 09 Dec 1992 20:09
33 lines
1575 bytes
1575 bytes
Hello there,
I am trying to compile some code I ftp'd off of the internet and it
is written in standard traditional C (non-ANSI). I use the -taditional
option when compiling the code and I also supply the option -U__GNUC__.
In the GNU CC manual, under the '-traditional' option, it states:
o In the preprocessor, macro arguments are recognized within string
constants in a macro definition ( and their values are stringified,
though without additional quote marks, when they appear in such a
context). The preprocessor always considers a string constant to end
at a newline.
If this is true, should the following lines of code, at compile time
produce what I have stated below?
#define PARSE_ENUM(Type) \
static int \
parse_enum_\
Type(str, res) \
char *str; \
int **res; \
{ \
return parse_enum(str, enum_MIB_\
Type, res); \
}
PARSE_ENUM(IfType)
/* The preprocessor [should] produce:
static int parse_enum_IfType(str, res) char *str; int **res; {\
return parse_enum(str, enum_MIB_IfType, res)); }
*/
Technical Details
Message-ID:
<199212092009.AA18509@harvey.gte.com>Path:
arc1-ca.pugleaf.net!sparky!uunet!cis.ohio-state.edu!gte.com!wjb4Show Full Headers
Complete Article Headers
X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 11318c,b7fc6aaa74dfcd7d,start X-Google-Attributes: gid11318c,public X-Google-ArrivalTime: 1992-12-09 18:32:49 PST Newsgroups: gnu.gcc.help Path: arc1-ca.pugleaf.net!sparky!uunet!cis.ohio-state.edu!gte.com!wjb4 From: wjb4@gte.com Subject: GNU CC traditional option Message-ID: <199212092009.AA18509@harvey.gte.com> Sender: gnulists@ai.mit.edu Organization: GNUs Not Usenet Distribution: gnu Date: Wed, 9 Dec 1992 20:09:36 GMT Lines: 35