Smylers wrote:
Ken Fox wrote:
How about formalizing global namespace pollution with something like
the Usenet news group formation process? Ship Perl 6 with a very
small number of global symbols and let it grow naturally.
If the initial release of Perl 6 doesn't have commonly-required
functions then people will write their own. People will do these in
incompatible ways ...
You're taking that out of context. Ship the commonly required
functionality, but don't introduce new global symbols.
A global C<push> function:
push @array, 1
A class C<push> method:
push @array: 1
Methods work well with AUTOLOAD, so they probably don't require
C<use> statements. Anyways, I'd rather have C<use> statements than
globals. I know others disagree -- I even disagree when I'm
trying to write a one-liner on the command line.
Perl 6 is the community rewrite. One of the pillars of the
community is CPAN. Could CPAN help resolve simple library and
namespace issues? Adding C<purge> or C<part> is not a language
design issue.
- Ken
