This is the mail archive of the
mailing list for the libstdc++ project.
Re: Problem with `string', threading and shared libraries.
- To: Loren James Rittle <rittle at latour dot rsch dot comm dot mot dot com>
- Subject: Re: Problem with `string', threading and shared libraries.
- From: Gabriel Dos Reis <gdr at codesourcery dot com>
- Date: 02 Oct 2001 09:26:26 +0200
- Cc: libstdc++ at gcc dot gnu dot org
- Organization: CodeSourcery, LLC
- References: <20010928164914.A32098@alinoe.com> <200110020138.f921cCK45265@latour.rsch.comm.mot.com>
Loren James Rittle <firstname.lastname@example.org> writes:
| In article <email@example.com> you write:
| >Carlo Wood <firstname.lastname@example.org> writes:
| >| I really think that it was a wrong decision to include
| >| thread-safeness in the mangling of std::string.
| > So we're at least two then.
| When you agree with Carlo on this matter, be sure you fully understand
| what you are agreeing to.
| He had compiled libstdc++ with a macro, reserved to the
| implementation, defined and then he compiled his user code without
| that macro defined. Nowhere do we document that macro being used by
| normal users of the library.
Thanks for the clarification. I guess I need to clarify my position
as well: I don't think --enable-threads should change std::string