According to Chip Salzenberg:
> According to TOGoS:
> > Or explicit exports :) that way you only need to define the
> > interface once, and then all unified-namespace languages can use it.
>
> Asking Perl programmers to go out of their way to present foreign and
> unnatural interfaces is, well, foreign and unnatural for Parrot.
However, I should add that I'm sure there will certainly be some
convenience tools provided very early on, which will do most of the
"usual" and "expected" things for common cases.
For example, I'd be really surprised if there weren't a wrapper
created quickly by someone[*] so that in Python you could say:
import perl5.File.Path
and get the appearance of what you asked for in your previous message:
all the exported Perl functions and variables, but without the sigils.
But my point is that the namespace mechanism need not provide much
support (or any, really) for this to work.
[*] Wrappers and adapters are all the rage in free software these
days. (Whatever memetic plage it is that afflicts Java people
seems to be contagious.) So it won't take long for people to write
what I'm describing. Heck, we might do it ourselves, just so we
can test the low-level interoperations more conveniently.
--
Chip Salzenberg - a.k.a. - <[EMAIL PROTECTED]>
"I don't really think it is a question of bright people and dumb
people, but rather people who can see the game they're playing and
those who can't." -- Joe Cosby
