On Thu, Aug 15, 2013 at 03:40:01PM +0000, Per Hedbor () @ Pike (-) developers forum wrote:
The major issue with this is that pike have shared strings (and this, incidentally, makes the whole concept of 'secure' strings rather odd, they should have been a separate class entirely).
i thought that was the case, at least my impression from the discussion about it was that once a string was marked secure, it would no longer be shared.
certainly a simple string should not become secure just because its contents happens to be the same as another one somewhere else entirely that is secure.
what should happen is that if i add a secure string to a non-secure one, the new string should be secure too, and no-longer shared.
greetings, martin.