This is the mail archive of the
mailing list for the GCC project.
Re: [Patch] Fix wrong backup variable initialization in regex
- From: Paolo Carlini <paolo dot carlini at oracle dot com>
- To: Tim Shen <timshen91 at gmail dot com>
- Cc: libstdc++ <libstdc++ at gcc dot gnu dot org>, gcc-patches <gcc-patches at gcc dot gnu dot org>
- Date: Fri, 04 Oct 2013 00:41:56 +0200
- Subject: Re: [Patch] Fix wrong backup variable initialization in regex
- Authentication-results: sourceware.org; auth=none
- References: <CAPrifD==3q9Ysedyj5Zbmex26RXTazraN2TNKanXji4XcpRcpQ at mail dot gmail dot com> <524DD5EF dot 5080905 at oracle dot com> <CAPrifD=B8RuF5fPMRbV7XYBsHOJc+sOv1Q2qS7m2BfK2QkN+-g at mail dot gmail dot com> <524DE448 dot 7090109 at oracle dot com> <CAPrifDnoAs7VeVtVziHwYP-zLK-+St5YvCHg-8hozE2D_6ytXg at mail dot gmail dot com>
Tim Shen <email@example.com> ha scritto:
>Yes I think we should keep secret, because the standard doesn't
>specify it. They only way to publish the switch to user is making a
>library extension(is that true?), but there's no obvious benefit to do
>that(is that true? I shall be humble).
Well, the standard doesn't specify it, but that doesn't mean that it does forbid it! If you add a mechanism which uses a mangled name, doesn't require additional template parameters for its implementation, etc, and you document it, everything is perfectly fine. I think that, if only for our internal use (eg, in the testsuite!) it would be quite convenient to have a mechanism which forces the switch, to wit bypasses the automatic switch having to do with brs. And even if at this time it may not make much sense for the users to choose (because one is certainly much faster and only the other correctly handles brs) that may not be so obvious if you add a third.