This is the mail archive of the
libstdc++@gcc.gnu.org
mailing list for the libstdc++ project.
Re: [PING] Add const char* constructors for exception classes in <stdexcept>
- From: Oleg Endo <oleg dot endo at t-online dot de>
- To: Jonathan Wakely <jwakely dot gcc at gmail dot com>
- Cc: "libstdc++ at gcc dot gnu dot org" <libstdc++ at gcc dot gnu dot org>, gcc-patches <gcc-patches at gcc dot gnu dot org>
- Date: Sun, 11 May 2014 21:01:33 +0200
- Subject: Re: [PING] Add const char* constructors for exception classes in <stdexcept>
- Authentication-results: sourceware.org; auth=none
- References: <1387411826 dot 2455 dot 325 dot camel at yam-132-YW-E178-FTW> <CAH6eHdTK93RwatvT+m_1TLv7Ni=yQ=wDi6v7Hq=jT=O=ZSffzw at mail dot gmail dot com> <1387466908 dot 2455 dot 355 dot camel at yam-132-YW-E178-FTW> <1390745736 dot 22215 dot 207 dot camel at yam-132-YW-E178-FTW> <20140129152136 dot GA21735 at redhat dot com> <1391030247 dot 13654 dot 9 dot camel at yam-132-YW-E178-FTW> <CAH6eHdQXvD27Y83cpEtoJRH7=3mAfujzd4=GKDBiT-G08SK-pg at mail dot gmail dot com> <1391035518 dot 13654 dot 34 dot camel at yam-132-YW-E178-FTW> <1398961092 dot 2451 dot 28 dot camel at yam-132-YW-E178-FTW> <CAH6eHdTzYxKXcbBhOCzTwvSDNNff5v3B77K+cuHkK3=-2Yxsdw at mail dot gmail dot com>
On 02 May 2014, at 17:57, Jonathan Wakely <jwakely.gcc@gmail.com> wrote:
> On 1 May 2014 17:18, Oleg Endo wrote:
>> Jonathan,
>>
>> now that we're in stage 1 again, I'd like to revive the issue below. Do
>> you have any particular plans? How should we proceed?
>
> Hi Oleg, sorry for letting the thread die in January.
>
> We will definitely want to deal with the missing constructors in
> <stdexcept> during stage 1, but I'm not sure exactly when :-)
>
> I'll come back to this next week - ping me if you don't hear from me again!
And here I am, pinging... :)
If it helps, I could brush up the patch that I submitted here:
http://gcc.gnu.org/ml/gcc-patches/2013-12/msg01688.html
The thing you've mentioned regarding exception message string storage in
http://gcc.gnu.org/ml/gcc-patches/2014-01/msg01925.html
is a different issue I think.
Cheers,
Oleg