Re: You never have privacy from your children in Perl 6

Am Dienstag, den 23.03.2010, 20:06 +0100 schrieb Moritz Lenz: > > Carl Mäsak wrote: > > Carl (>>), Moritz (>): > >>> um, so 'protected' is when the deriving classes can see the > >>> attribute? > >>> yup > >>> that's what 'private' means in Perl 6. > >> > >> That's wrong. Perl 6's "private" i

r30180 - docs/Perl6/Spec

Author: moritz Date: 2010-03-23 21:13:55 +0100 (Tue, 23 Mar 2010) New Revision: 30180 Modified: docs/Perl6/Spec/S12-objects.pod Log: [S12] document that "trusts" traits do not extend to child classes, as per TimToady++ Modified: docs/Perl6/Spec/S12-objects.pod

Re: You never have privacy from your children in Perl 6

Em Ter, 2010-03-23 às 20:53 +0100, Moritz Lenz escreveu: > unless you count 'trusts' > traits, which are specific to single classes, not groups of subclasses Yes, that was what I meant... daniel

Re: You never have privacy from your children in Perl 6

Daniel Ruoso wrote: > Em Ter, 2010-03-23 às 19:41 +0100, Carl Mäsak escreveu: >> um, so 'protected' is when the deriving classes can see the >> attribute? >> yup >> that's what 'private' means in Perl 6. >> what? so there's only really 'public' and 'protected', but no >> 'private'? >> basicall

Re: You never have privacy from your children in Perl 6

Em Ter, 2010-03-23 às 19:41 +0100, Carl Mäsak escreveu: > um, so 'protected' is when the deriving classes can see the > attribute? > yup > that's what 'private' means in Perl 6. > what? so there's only really 'public' and 'protected', but no > 'private'? > basically, yes. although 'protected'

Re: You never have privacy from your children in Perl 6

Carl Mäsak wrote: > Carl (>>), Moritz (>): >>> um, so 'protected' is when the deriving classes can see the >>> attribute? >>> yup >>> that's what 'private' means in Perl 6. >> >> That's wrong. Perl 6's "private" is like Java's "private" - subclasses >> can't see it. >> It's just Rakudo being

Re: You never have privacy from your children in Perl 6

Carl (>>), Moritz (>): >> um, so 'protected' is when the deriving classes can see the >> attribute? >> yup >> that's what 'private' means in Perl 6. > > That's wrong. Perl 6's "private" is like Java's "private" - subclasses > can't see it. > It's just Rakudo being leaky at the moment, not a fal

Re: You never have privacy from your children in Perl 6

Carl Mäsak wrote: > um, so 'protected' is when the deriving classes can see the attribute? > yup > that's what 'private' means in Perl 6. That's wrong. Perl 6's "private" is like Java's "private" - subclasses can't see it. It's just Rakudo being leaky at the moment, not a fallacy of the Perl 6

You never have privacy from your children in Perl 6

Wanting to run the recent class-attribute discussion[0] through the neural net of my friend, I described to him in detail how the current system with attributes works. He's kind of a Java guy, and though he liked the twigil distinction between private and public, he asked how to produce a 'protecte

Re: Something about the cascade calling of sort() in rakudo.

2010/3/23 Moritz Lenz : > Hi, > > Hongwen Qiu wrote: >> Hi, I'm new to Perl6. And just ran the first example in the perl6 book. >> But, it refused to work. It complains as follows: >> >> Too many positional parameters passed; got 2 but expected between 0 and 1 >> >> I find out that the problem is i

Re: Something about the cascade calling of sort() in rakudo.

Hi, Hongwen Qiu wrote: > Hi, I'm new to Perl6. And just ran the first example in the perl6 book. > But, it refused to work. It complains as follows: > > Too many positional parameters passed; got 2 but expected between 0 and 1 > > I find out that the problem is in the line: > > my @sorted = @na

Something about the cascade calling of sort() in rakudo.

Hi, I'm new to Perl6. And just ran the first example in the perl6 book. But, it refused to work. It complains as follows: Too many positional parameters passed; got 2 but expected between 0 and 1 I find out that the problem is in the line: my @sorted = @names.sort({ %sets{$_} }).sort({ %games{$_