- Original Message
As far as I know, Perl6Array should _not_ be showing up in
Perl 6's namespace, and if it is doing so, that's a reportable
bug.
I was just being sloppy. I was using that in PIR, not Rakudo, and I mistyped
the type -- er, I wrote the wrong class name in writing
Ovid wrote:
Is it possible to modify the core Perl6Array class like that (without extra
keywords)? If so, is it possible for each programmer to make such a change
so that it's lexically scoped?
AFAIK, it is not possible to modify a core class; however, I believe
that it _is_ possible to
- Original Message
From: Moritz Lenz mor...@faui2k3.org
That is the preferred way to avoid action-at-a-distance in P6.
so if I do that, will a 'my @a' use that new Array class?
Actually I'd prefer it if there were some kind of mechanism to set a
default implementation type, so
Ovid wrote:
Actually, I'd prefer to go much further than this:
use Core 'MyCore';
And have that override core classes lexically.
That solves the but I want it MY way issue that many Perl and Ruby
programmers have, but they don't shoot anyone else in the foot.
Since 'use' imports its
- Original Message
From: Jon Lang datawea...@gmail.com
Actually, I'd prefer to go much further than this:
use Core 'MyCore';
And have that override core classes lexically.
That solves the but I want it MY way issue that many Perl and Ruby
programmers have, but they
On Mon, Jan 12, 2009 at 02:43:37PM -0800, Ovid wrote:
: Actually, I'd prefer to go much further than this:
:
: use Core 'MyCore';
:
: And have that override core classes lexically.
We're already speccing a way to substitute a different prelude from
the command line, in order to desugar -n and
Ovid wrote:
- Original Message
From: Jon Lang datawea...@gmail.com
Actually, I'd prefer to go much further than this:
use Core 'MyCore';
And have that override core classes lexically.
That solves the but I want it MY way issue that many Perl and Ruby
programmers have,
On Mon, Jan 12, 2009 at 04:38:07PM -0800, Jon Lang wrote:
: No, you don't understand me. The Foo/Bar example I was giving was
: independent of your example. Rephrasing in your terms, consider the
: possibility of a class that's derived from Array, for whatever reason;
: call it Ring. Now you
