In any case, for the whole "future compatability" issue, which would be
prefered, double colon in the string, semicolon separating strings, or
null characters in strings?
> In any case, for the whole "future compatability" issue, which would
> be prefered, double colon in the string, semicolon separating strings,
> or null characters in strings?
A namespace 'Foo::Bar' is just one, albeit funny, name and inaccessible
for languages like Python (without a wrapper). [1]
['Foo' ; 'Bar'] denotes a nested namespace and is totally different. [2]
A key with a leading NUL: "\0Foo" denotes the name of a nested
namespace hash. This is just an internal convention to be able to store
a variable name 'Foo' in the same namespace. [3]
%globals = {
'Foo::Bar' => $P1, # [1]
"\0Foo" => { "\0Bar => $P2 }, # [2]
'Foo', # [3]
}
HTH,
leo