On Mon, Aug 27, 2001 at 06:42:28PM -0700, Mark D. Anderson wrote:
> > This may not work.
> >...
> > Some of those compilers
> > would NOT let you '#ifdef' out the version that it did not recognize
> > (perhaps thinking that '#warn' or '#warning' might be some gross typo
> > for '#else' or '#endif'
"Mark D. Anderson" wrote:
> > This may not work.
> >...
> > Some of those compilers
> > would NOT let you '#ifdef' out the version that it did not recognize
> > (perhaps thinking that '#warn' or '#warning' might be some gross typo
> > for '#else' or '#endif', I guess...).
>
> this is true; some c
> This may not work.
>...
> Some of those compilers
> would NOT let you '#ifdef' out the version that it did not recognize
> (perhaps thinking that '#warn' or '#warning' might be some gross typo
> for '#else' or '#endif', I guess...).
this is true; some compilers seem to require that #ifdef'd out
At 1:47 PM -0500 8/27/01, Alfred Perlstein wrote:
>* Charles Randall <[EMAIL PROTECTED]> [010827 12:44] wrote:
>> I've noted that several include files in /usr/include use the C preprocessor
>> #warning directive. This isn't standard C and prevents some software from
>> compiling using a compil
* Charles Randall <[EMAIL PROTECTED]> [010827 12:44] wrote:
> I've noted that several include files in /usr/include use the C preprocessor
> #warning directive. This isn't standard C and prevents some software from
> compiling using a compiler like TenDRA. What's the current opinion on this?
My o
I've noted that several include files in /usr/include use the C preprocessor
#warning directive. This isn't standard C and prevents some software from
compiling using a compiler like TenDRA. What's the current opinion on this?
Charles
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscr
6 matches
Mail list logo
