From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 8554 invoked by alias); 2 Nov 2010 18:01:27 -0000 Received: (qmail 8544 invoked by uid 22791); 2 Nov 2010 18:01:26 -0000 X-SWARE-Spam-Status: No, hits=-2.0 required=5.0 tests=AWL,BAYES_00,TW_FN X-Spam-Check-By: sourceware.org Received: from rock.gnat.com (HELO rock.gnat.com) (205.232.38.15) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Tue, 02 Nov 2010 18:01:22 +0000 Received: from localhost (localhost.localdomain [127.0.0.1]) by filtered-rock.gnat.com (Postfix) with ESMTP id 7AACE2BAB61; Tue, 2 Nov 2010 14:01:20 -0400 (EDT) Received: from rock.gnat.com ([127.0.0.1]) by localhost (rock.gnat.com [127.0.0.1]) (amavisd-new, port 10024) with LMTP id wTa1GBl2rqfq; Tue, 2 Nov 2010 14:01:20 -0400 (EDT) Received: from joel.gnat.com (localhost.localdomain [127.0.0.1]) by rock.gnat.com (Postfix) with ESMTP id 12AC22BACC8; Tue, 2 Nov 2010 14:01:16 -0400 (EDT) Received: by joel.gnat.com (Postfix, from userid 1000) id 97BF8F588F; Tue, 2 Nov 2010 11:01:10 -0700 (PDT) Date: Tue, 02 Nov 2010 18:01:00 -0000 From: Joel Brobecker To: Doug Evans Cc: Jan Kratochvil , gdb-patches@sourceware.org, Ken Werner , Tom Tromey , Pedro Alves Subject: Re: [doc RFA] Switch to GCC coding style [Re: [patch] initial OpenCL C language support] Message-ID: <20101102180110.GB2492@adacore.com> References: <201010221920.30046.ken@linux.vnet.ibm.com> <20101026195747.GE2847@adacore.com> <20101027190417.GA19067@host1.dyn.jankratochvil.net> <201010272020.51386.pedro@codesourcery.com> <20101102165134.GA19296@host0.dyn.jankratochvil.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.20 (2009-06-14) Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sourceware.org X-SW-Source: 2010-11/txt/msg00029.txt.bz2 > There are lots of things on the gcc codingconventions page that need > to be converted (e.g., gcc_assert), or revised (e.g., prototypes for > _initialize_foo fns can appear in .c files (and should *only* appear > in .c files)). > > I'm not sure, but it might be simpler to just copy over the relevant bits. This is something I was thinking about as well. I think we should have our own Wiki page for conventions. That way, we can document our own specific requirements (gdb_assert, etc). -- Joel