On Jan 5, 2006, at 0:49, Joshua Isom wrote:
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
The PIR syntax.pod file says that nested namespaces can be used by
separating namespaces with a semicolon, ala nested array/hash
structures. But the common writing convention seems to be along the
lines of perl5 packages with a double colon to separate. After looking
at the "find_global Foo::
