S12 says (in the context of classes):
my method think (Brain $self: $thought)
(Such methods are completely invisible to ordinary method calls, and are
in fact called with a different syntax that uses ! in place of the .
character. See below.)
And later on, in the context of roles:
my
and a few more thoughts:
I wrote:
S12 says (in the context of classes):
my method think (Brain $self: $thought)
(Such methods are completely invisible to ordinary method calls, and are
in fact called with a different syntax that uses ! in place of the .
character. See below.)
for
-Original Message-
From: chromatic [mailto:[EMAIL PROTECTED]
We are trying to avoid the java.lang.String is Final
problem here in various ways. One of them is not allowing
library designers to mark things as final.
Overloading final was Java's rather inept attempt to define
I wrote:
Overloading final was Java's rather inept attempt to
define objects with value semantics rather than container semantics
John M. Dlugosz [EMAIL PROTECTED] wrote:
Can you tell me more about that, or point to something?
Alas I can't point to anything, it's just a personal
Brandon Allbery allbery-at-kf8nh.com |Perl 6| wrote:
S06/Lvalue subroutines: Lvalue subroutines return a proxy object
that can be assigned to. (...)
S13/Methods: Setter methods that expect the new value as an argument
do not fall into the well-behaved category, however.
When I take these
Kealey, Martin, ihug-NZ Martin.Kealey-at-vodafone.com |Perl 6| wrote:
In Java, final is used to denote both a *class* that can't change (extend),
and *value* that can't change (a constant member of the class).
Got it: on a value it means readonly.
--John
Moritz Lenz moritz-at-casella.verplant.org |Perl 6| wrote:
S12 says (in the context of classes):
my method think (Brain $self: $thought)
(Such methods are completely invisible to ordinary method calls, and are
in fact called with a different syntax that uses ! in place of the .
character.
