Update of bug #35699 (project gnustep):
Status: None => Fixed
Open/Closed: Open => Closed
_______________________________________________________
Follow-up Comment #2:
More a compatibility issue than a bug ... but in this case it's a probably a
better behaviour too. AFAIK this is an undocumented feature (I've never heard
of it before), so perhaps we should document it?
I've always considered the NoCopy/freeWhenDone=NO method to be a variant for
use with constant buffers, and code which uses non-constant buffers to be
buggy (i.e. an app error to do that) unless it *really* knows what it's
doing.
But the behaviour of implicitly copying in this situation is certainly more
fault tolerant.
It still doesn't deal with the case of code which modifies the buffer while
the original string is using it, but such code is plainly asking for trouble
:-)
_______________________________________________________
Reply to this item at:
<http://savannah.gnu.org/bugs/?35699>
_______________________________________________
Message sent via/by Savannah
http://savannah.gnu.org/
_______________________________________________
Bug-gnustep mailing list
Bug-gnustep@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-gnustep
