From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 18396 invoked by alias); 14 Sep 2004 18:58:45 -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 18383 invoked from network); 14 Sep 2004 18:58:44 -0000 Received: from unknown (HELO mproxy.gmail.com) (64.233.170.200) by sourceware.org with SMTP; 14 Sep 2004 18:58:44 -0000 Received: by mproxy.gmail.com with SMTP id 77so63801rnl for ; Tue, 14 Sep 2004 11:58:44 -0700 (PDT) Received: by 10.38.126.67 with SMTP id y67mr272076rnc; Tue, 14 Sep 2004 11:58:44 -0700 (PDT) Received: by 10.38.171.25 with HTTP; Tue, 14 Sep 2004 11:58:44 -0700 (PDT) Message-ID: <84fc9c00040914115855cad428@mail.gmail.com> Date: Tue, 14 Sep 2004 19:17:00 -0000 From: Richard Guenther Reply-To: Richard Guenther To: Wolfgang Bangerth Subject: Re: Style of libstdc++ header files Cc: gcc@gcc.gnu.org, libstdc++@gcc.gnu.org, bugzilla-masters@dberlin.org In-Reply-To: <200409141350.43359.bangerth@ices.utexas.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit References: <200409141350.43359.bangerth@ices.utexas.edu> X-SW-Source: 2004-09/txt/msg00873.txt.bz2 On Tue, 14 Sep 2004 13:50:43 -0500, Wolfgang Bangerth wrote: > > My request therefore would be if the libstdc++ people could comment if it is > possible to gradually move away from their style of using inlined function > definitions, and towards a style where function declarations and definitions > are always clearly separated. I understand that this is a huge change, but > one that could make the life of us bugmasters so much easier! I would oppose to that as atleast short always-to-be-inlined methods are way easier to read/find if they are defined inline. I'd rather spent the converting time creating a more C++-syntax aware testcase-reduction tool (like f.i. as you are suggesting, removing method definitions but retaining/creating declarations). If our C++ parser would only be so readable to be able to reproduce source - I tried for a weekend, but miserably failed to even get to the point of just re-outputting recognized tokens... Richard.