From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 16320 invoked by alias); 27 May 2005 00:54:39 -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 15879 invoked by uid 22791); 27 May 2005 00:54:30 -0000 Received: from ds01.webmacher.de (HELO ds01.webmacher.de) (213.239.192.226) by sourceware.org (qpsmtpd/0.30-dev) with ESMTP; Fri, 27 May 2005 00:54:30 +0000 Received: from [192.168.0.194] (dialin-145-254-148-196.arcor-ip.net [145.254.148.196]) by ds01.webmacher.de (Postfix) with ESMTP id 943984441A5; Fri, 27 May 2005 02:58:34 +0200 (CEST) In-Reply-To: References: Mime-Version: 1.0 (Apple Message framework v730) Content-Type: text/plain; charset=US-ASCII; format=flowed Message-Id: <67DEACEB-9B45-453A-86F4-CE0676744737@dalecki.de> Cc: gcc@gcc.gnu.org, jason@redhat.com, mark@codesourcery.com, dberlin@dberlin.org Content-Transfer-Encoding: 7bit From: Marcin Dalecki Subject: Re: Compiling GCC with g++: a report Date: Fri, 27 May 2005 01:20:00 -0000 To: Gabriel Dos Reis X-SW-Source: 2005-05/txt/msg01473.txt.bz2 On 2005-05-23, at 08:15, Gabriel Dos Reis wrote: > > > Sixth, there is a real "mess" about name spaces. It is true that > every C programmers knows the rule saying tags inhabit different name > space than variable of functions. However, all the C coding standards > I've read so far usually suggest > > typedef struct foo foo; > > but *not* > > typedef struct foo *foo; > > i.e. "bringing" the tag-name into normal name space to name the type > structure or enumeration is OK, but not naming a different type! the > latter practice will be flagged by a C++ compiler. I guess we may > need some discussion about the naming of structure (POSIX reserves > anything ending with "_t", so we might want to choose something so > that we don't run into problem. However, I do not expect this issue > to dominate the discussion :-)) > In 80% of the cases you are talking about the GCC source code already follows the semi-convention of appending _s to the parent type.