trying to use a role within a role

Could someone please tell me what is wrong with the following? role win_text { has $.win_mytxt1 is rw; has $.win_mytxt2 is rw; }; role mywindow { has $.border is rw; has $.colour is rw; does win_text; }; my $w = new mywindow; $w.border = 2; $w.colour = 'red'; say $w.border; say $w.colour;

Re: [perl #40438] Extending a dynpmc with a PIR method fails

The attached patch is my first step at locating bug #40438. It adds pdump -d functionality for keys. Leopold Toetsch via RT wrote: Thanks, I've applied a modified version of the patch, showing that it's a namespace issue caused by the .HLL line. Using .loadlib works fine and as expected. leo

Re: class interface of roles

TSa wrote: > HaloO, > > is this subject not of interest? I just wanted to start a > discussion about the class composition process and how a > role designer can require the class to provide an equal > method and then augment it to achieve the correct behavior. > Contrast that with the need to do th

Re: [perl #40429] [PATCH] test for perl code coda

Will, Thank you for your work on this: it's a solid patch, I'd apply it... ... But I've just rolled this test into the recently added t/codingstd/perlcritic.t by way of a Perl::Critic policy class that's been added to the repo. Please don't be discouraged. =-) I'm not! :-) Thanks for the p

[perl #40443] Separate vtable functions from methods (using :vtable)

# New Ticket Created by Matt Diephouse # Please include the string: [perl #40443] # in the subject line of all future correspondence about this issue. # http://rt.perl.org/rt3/Ticket/Display.html?id=40443 > At the OSCON 2006 Hackathon, it was decided that we should separate vtables from met

Perl 6 mailing list summary, 24-30 September, 2006

This week on the Perl 6 mailing lists "And here I thought you were a responsible, law-abiding citizen... :P " -- Jonathan Lang, commenting on Larry Wall's `self.HOW does Hash` Language class interface of roles TSa wondered how typing of mixins

Abstract roles, classes and objects

Trey Harris wrote: In a message dated Fri, 29 Sep 2006, Aaron Sherman writes: That said, this is a different point, above and I think it's an easy one to take on. role A { method x() {...} } class B { does A; } does generate an error per "If a role merely declares methods without defining t

Re: [svn:parrot-pdd] r14784 - trunk/docs/pdds/clip

Hi all, It crossed my mind that we could do this, but I rejected it since it's not really helpful. The #! line is generally only applicable to UNIX-y systems. Even on those systems that do support it, the path to Parrot won't always be the same either. Just a little trick that can help. If

Re: Motivation for /+/ set Array not Match?

Audrey (>), Carl (>>): > Has this been settled or addressed off-list? 'fraid not yet... Ah. So Warnock applies. (Side note: when I first read "Warnock applies" on things in p6 summaries a year or so ago, I thought it was some really energetic programmer who went around and applied patches as

Re: Motivation for /+/ set Array not Match?

在 Sep 28, 2006 3:03 AM 時，Carl Mäsak 寫到： Audrey (>): Indeed... Though what I'm wondering is, is there a hidden implementation cost or design cost of making /+/ always behave such that $.from returns something, compared to the current treatment with the workaround you suggested? Has this

[perl #40438] Extending a dynpmc with a PIR method fails

Thanks, I've applied a modified version of the patch, showing that it's a namespace issue caused by the .HLL line. Using .loadlib works fine and as expected. leo

Re: Synopses on the smoke server are a bit out-of-date

Hi, Agent Zhang wrote: > On 9/28/06, Agent Zhang <[EMAIL PROTECTED]> wrote: >> lanny noticed yesterday that the Synopses on the smoke server were >> different from the ones on feather. Because I am maintaining the >> feather ones, I know the synopses there are being resync'd every hour >> as expec

Re: Automatic coercion and context

Jonathan Scott Duff wrote: I hope you're way off the mark. Automatic coercion was one of the annoyances I remember from C++. Debugging becomes more difficult when you have to not only chase down things that are a Foo, but anything you've compiled that might know how to turn itself into a Foo. O