From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 6201 invoked by alias); 10 Dec 2003 13:34:26 -0000 Mailing-List: contact gcc-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Archive: List-Post: List-Help: Sender: gcc-owner@gcc.gnu.org Received: (qmail 6194 invoked from network); 10 Dec 2003 13:34:25 -0000 Received: from unknown (HELO uniton.integrable-solutions.net) (62.212.99.186) by sources.redhat.com with SMTP; 10 Dec 2003 13:34:25 -0000 Received: from uniton.integrable-solutions.net (localhost [127.0.0.1]) by uniton.integrable-solutions.net (8.12.3/8.12.3/SuSE Linux 0.6) with ESMTP id hBADUe9b002298; Wed, 10 Dec 2003 14:30:40 +0100 Received: (from gdr@localhost) by uniton.integrable-solutions.net (8.12.3/8.12.3/Submit) id hBADUcIg002297; Wed, 10 Dec 2003 14:30:38 +0100 X-Authentication-Warning: uniton.integrable-solutions.net: gdr set sender to gdr@integrable-solutions.net using -f To: Segher Boessenkool Cc: Robert Dewar , gcc@gcc.gnu.org, Eyal Lebedinsky , Andreas Schwab , Michael Elizabeth Chastain Subject: Re: (printf) ("hello world\n"); References: <20031209204037.906D84B412@berman.michael-chastain.com> <3FD6DD9B.E35C742@eyal.emu.id.au> <3FD71140.2070506@gnat.com> From: Gabriel Dos Reis In-Reply-To: Organization: Integrable Solutions Date: Wed, 10 Dec 2003 13:36:00 -0000 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-SW-Source: 2003-12/txt/msg00626.txt.bz2 Segher Boessenkool writes: | 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? Put Andreas' statement in context and use 7.1.3 Reserved identifiers [...] -- All identifiers with external linkage in any of the following subclauses (including the future library directions) are always reserved for use as identifiers with external linkage.154) [...] [#2] No other identifiers are reserved. If the program declares or defines an identifier in a context in which it is reserved (other than as allowed by 7.1.4), or defines a reserved identifier as a macro name, the behavior is undefined.