bug-glibc
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: 3.0 wierdness


From: Andreas Jaeger
Subject: Re: 3.0 wierdness
Date: Thu, 20 Dec 2001 07:08:25 +0100
User-agent: Gnus/5.090004 (Oort Gnus v0.04) XEmacs/21.4 (Artificial Intelligence, i386-suse-linux)

Finny Merrill <address@hidden> writes:

> On Wed, 19 Dec 2001, mike stump wrote:
>
>> > Date: Wed, 19 Dec 2001 21:52:23 -0600 (CST)
>> > From: Finny Merrill <address@hidden>
>> > To: <address@hidden>
>> 
>> > printf is a macro? HOW does printf being a macro work ESPECIALLY
>> > since we can no longer put preprocessor constants in printf
>> > statements!
>> 
>> This isn't a gcc issue.  It is a library issue.
>> 
>> #undef printf
>> 
>> or
>> 
>> (printf)("...", ...)
>> 
>> but notice, in C++, last I looked, printf could not be a macro, nor
>> can you #undef it, even if it were.
>> 
> in C99 it can't be a macro either

Where is that written down in C99?  AFAIR C99 allows macros for all
functions.

An alternative solution: Upgrade to glibc 2.2.4, it removes the printf
macro from glibc,

Andreas

2001-08-02  Andreas Jaeger  <address@hidden>

        * libio/bits/stdio.h (printf): Remove printf optimization since
        GCC 3.0 can optimize printf.


-- 
 Andreas Jaeger
  SuSE Labs address@hidden
   private address@hidden
    http://www.suse.de/~aj



reply via email to

[Prev in Thread] Current Thread [Next in Thread]