From: Richard Guenther <richard.guenther@gmail.com>
To: Wolfgang Bangerth <bangerth@ices.utexas.edu>
Cc: gcc@gcc.gnu.org, libstdc++@gcc.gnu.org, bugzilla-masters@dberlin.org
Subject: Re: Style of libstdc++ header files
Date: Tue, 14 Sep 2004 19:17:00 -0000 [thread overview]
Message-ID: <84fc9c00040914115855cad428@mail.gmail.com> (raw)
In-Reply-To: <200409141350.43359.bangerth@ices.utexas.edu>
On Tue, 14 Sep 2004 13:50:43 -0500, Wolfgang Bangerth
<bangerth@ices.utexas.edu> 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.
next prev parent reply other threads:[~2004-09-14 18:58 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-14 19:11 Wolfgang Bangerth
2004-09-14 19:17 ` Richard Guenther [this message]
2004-09-14 19:17 ` Theodore Papadopoulo
2004-09-14 19:22 ` Wolfgang Bangerth
2004-09-14 19:20 ` Wolfgang Bangerth
2004-09-14 19:24 ` Daniel Berlin
2004-09-14 19:44 ` Wolfgang Bangerth
2004-09-17 17:43 ` Benjamin Kosnik
2004-09-17 19:27 ` Mark Mitchell
2004-09-17 19:57 ` Gabriel Dos Reis
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=84fc9c00040914115855cad428@mail.gmail.com \
--to=richard.guenther@gmail.com \
--cc=bangerth@ices.utexas.edu \
--cc=bugzilla-masters@dberlin.org \
--cc=gcc@gcc.gnu.org \
--cc=libstdc++@gcc.gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).