Marcus Comstedt (ACROSS) (Hail Ilpalazzo!) @ Pike (-) developers forum wrote:
The way (shared) secure strings work now is that when "hej" is turned into a secured string, the string object "hej" in the shared string pool gets marked as "secure". This object is referenced by all strings "hej", secure or not. The flag remains on the string object until it all references to "hej" are gone and the string object is freed (at which time the actual string is zeroed over, this is the "secure" feature).
I see. Ok, that is useful in its own right. The only problem that arises here is that if you are (ab)using this marker to suppress casual display of the string, then if this string just happens to be the same as some other (unsecured) string, then the printing of the unsecured string is going to be prohibited as well (all of a sudden), which is confusing at best.