This is the mail archive of the gcc@gcc.gnu.org mailing list for the GCC project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: (printf) ("hello world\n");

From: Robert Dewar <dewar at gnat dot com>
To: Segher Boessenkool <segher at kernel dot crashing dot org>
Cc: gcc at gcc dot gnu dot org, Eyal Lebedinsky <eyal at eyal dot emu dot id dot au>,Andreas Schwab <schwab at suse dot de>,Michael Elizabeth Chastain <mec dot gnu at mindspring dot com>
Date: Wed, 10 Dec 2003 08:11:21 -0500
Subject: Re: (printf) ("hello world\n");
References: <20031209204037.906D84B412@berman.michael-chastain.com> <jmvfopy2un.fsf@desire.geoffk.org> <3FD6DD9B.E35C742@eyal.emu.id.au> <jeiskpxal1.fsf@sykes.suse.de> <3FD71140.2070506@gnat.com> <BB215256-2B0E-11D8-8ABB-000A95A4DC02@kernel.crashing.org>

Segher Boessenkool wrote:

On 10-dec-03, at 13:27, Robert Dewar wrote:
Is it really true that the name printf is reserved? Is a C program not
allowed to define its own printf function (which might or might not be
varargs)? What's the story here?
It is reserved only in translation units that have stdio.h #include'd.


Well that's not a matter of being reserved, just normal visibility
rules ...

References:
- (printf) ("hello world\n");
  - From: Michael Elizabeth Chastain
- Re: (printf) ("hello world\n");
  - From: Geoff Keating
- Re: (printf) ("hello world\n");
  - From: Eyal Lebedinsky
- Re: (printf) ("hello world\n");
  - From: Andreas Schwab
- Re: (printf) ("hello world\n");
  - From: Robert Dewar
- Re: (printf) ("hello world\n");
  - From: Segher Boessenkool

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]