public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Paolo Carlini <paolo.carlini@oracle.com>
To: stephen.webb@bregmasoft.ca
Cc: "Stephen M. Webb" <stephenw.webb@bregmasoft.ca>,
	 gcc-patches@gcc.gnu.org, libstdc++@gcc.gnu.org
Subject: Re: [v3] <regex> implementation foundation, version 2
Date: Tue, 22 Jun 2010 10:19:00 -0000	[thread overview]
Message-ID: <4C20899B.7020205@oracle.com> (raw)
In-Reply-To: <201006211458.23787.stephenw.webb@bregmasoft.ca>

On 06/21/2010 08:58 PM, Stephen M. Webb wrote:
> Version 2 of <regex>, now with the following:
>
> o  long lines have been fixed
> o  everything is now in headers (no ABI failures from library)
> o  more test cases
>   
Thanks.

Please add definiitions for those const static data members, I'm not
comfortable with playing such undefined behavior tricks just to spare a
few lines, in these times of whole program optimization, etc. It's
risky. I may bu guilty myself of some in the past, that's not an excuse.

Another change we should make, *.tcc files, by definition host *out of
line* functions: thus, the functions which we decided, for now at least,
to have inline in headers, should be simply defined in the class body,
in the *.h file. In any case, stuff like the _State constructors should
be inline anyway. I'm also seeing _M_lookup_classname, for example, out
of line, and it's also tiny. In general, remember, in our library *tiny*
functions are inline, and defined in the class body itself, in the *.h file.

Thanks,
Paolo.

  reply	other threads:[~2010-06-22 10:00 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-21 19:52 Stephen M. Webb
2010-06-22 10:19 ` Paolo Carlini [this message]
2010-06-22 11:17   ` Paolo Carlini

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=4C20899B.7020205@oracle.com \
    --to=paolo.carlini@oracle.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=libstdc++@gcc.gnu.org \
    --cc=stephen.webb@bregmasoft.ca \
    --cc=stephenw.webb@bregmasoft.ca \
    /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).