Re: Problem with using char* to return string by reference
- From: "Doug Harrison [MVP]" <dsh@xxxxxxxx>
- Date: Wed, 11 Jun 2008 13:14:33 -0500
On Wed, 11 Jun 2008 13:06:19 -0500, "Ben Voigt [C++ MVP]"
<rbv@xxxxxxxxxxxxx> wrote:
Not entirely sure that is sufficient to make it safe. Does the new wording
also prohibit string pooling/copy-on-write?
Long experience with the standard prohibits reference counting. The
standard itself has always prohibited copy-on-write.
--
Doug Harrison
Visual C++ MVP
.
- References:
- Problem with using char* to return string by reference
- From: swtbase
- Re: Problem with using char* to return string by reference
- From: Alex Blekhman
- Re: Problem with using char* to return string by reference
- From: Ben Voigt [C++ MVP]
- Re: Problem with using char* to return string by reference
- From: Alex Blekhman
- Re: Problem with using char* to return string by reference
- From: Giovanni Dicanio
- Re: Problem with using char* to return string by reference
- From: Norbert Unterberg
- Re: Problem with using char* to return string by reference
- From: Doug Harrison [MVP]
- Re: Problem with using char* to return string by reference
- From: Alf P. Steinbach
- Re: Problem with using char* to return string by reference
- From: Ben Voigt [C++ MVP]
- Problem with using char* to return string by reference
- Prev by Date: Re: dll won't work with VB6
- Next by Date: Re: Template const pointer argument C2440
- Previous by thread: Re: Problem with using char* to return string by reference
- Next by thread: Re: Problem with using char* to return string by reference
- Index(es):
Relevant Pages
|
