There's is a problem with the naming of classes and their associated namespaces
that must be addressed.
Creating Parrot classes currently requires _typed_ namespaces, that is,
namespaces where more than one object can have the same fully-qualified
name. Parrot's default namespace allows that ther
The documentation of the init_pmc() vtable method (a.k.a. '.sub __init_pmc'
for ParrotObjects) is inconsistent. In some places, the single PMC's
interpretation is simply described as "pmc-dependent"; in other places, it's
described as a set of properties, possibly keyed by number instead of name
[
On Tue, May 16, 2006 at 09:00:17AM -0700, Chip Salzenberg wrote:
> On Fri, Apr 14, 2006 at 06:17:01PM -0500, Patrick R. Michaud wrote:
> > How would you envision doing something like the following
> > Perl 6 in PIR?
> >
> > sub foo($x is rw) {
> >$x = new SomeClass
> > }
> >
> >
Author: chip
Date: Tue May 16 13:27:30 2006
New Revision: 12706
Modified:
trunk/docs/pdds/clip/pdd02_vtables.pod
trunk/docs/pdds/clip/pdd15_objects.pod
Changes in other areas also in this revision:
Modified:
trunk/docs/ROADMAP.pod
trunk/docs/vtables.pod
trunk/src/ops/ops.num
tru
On Tue, May 16, 2006 at 03:24:20PM -0500, Patrick R. Michaud wrote:
> On Tue, May 16, 2006 at 09:00:17AM -0700, Chip Salzenberg wrote:
> > On Fri, Apr 14, 2006 at 06:17:01PM -0500, Patrick R. Michaud wrote:
> > > How would you envision doing something like the following
> > > Perl 6 in PIR?
> > >
Chip Salzenberg wrote:
> On Tue, May 16, 2006 at 03:24:20PM -0500, Patrick R. Michaud wrote:
sub foo($x is rw) {
$x = new SomeClass
}
@z = 0..2;
foo( @z[1] );
>
> I sympathize with your desire for an answer, but it's probably a good idea
> for yo
On Wed, May 17, 2006 at 07:54:21AM +0800, Audrey Tang wrote:
> Chip Salzenberg wrote:
> > On Tue, May 16, 2006 at 03:24:20PM -0500, Patrick R. Michaud wrote:
> sub foo($x is rw) {
> $x = new SomeClass
> }
>
> @z = 0..2;
> foo( @z[1] );
>
> The a
Chip Salzenberg wrote:
>
> All that's needed is for the Perl 6 implementors to create a perl6;Scalar
> container that's more or less a translucent reference: It will handle
> assignment by switching to a new value, but it will handle most other
> operations by delegating to the value it currently
