With regard to the 'square' 'isa' 'rectangle' or vice versa question,
surely it is for the programmer to decide depending on the situation.
Though the problem is how to define criteria for trapping problems at
compile time.
Regarding classes and roles, and in fact multiple inheritance in
gene
Author: larry
Date: Sun Aug 27 22:52:36 2006
New Revision: 11504
Modified:
doc/trunk/design/syn/S02.pod
Log:
Clarification on syntactic mapping of and to ('a','b') and ('c').
Modified: doc/trunk/design/syn/S02.pod
On Aug 22, 2006, at 5:52 PM, John Siracusa wrote:
Has anyone looked at LLVM lately?
http://llvm.org/
I discovered it a few years ago. My personal interest is in the
portable C back end, so I can use the g++ compiler front end and send
the output through CodeWarrior or MPW compilers, whos
First, what's the recommended reference for learning how dispatching to
the right 'multi' sub is resolved. ?
I'd like to know the expected behavior in this case:
multi sub foo () { say "b: " }
multi sub foo () { say "a: " }
foo();
I would expect it would throw an error or at least a warning, sin
This week on the Perl 6 mailing lists
"My school's punch card machines were in the same room as the TRS-80
Model I ("THE COMPUTER ROOM"). These kids today with their hula hoops
and fax machines and intarwebs..."
-- Chip Salzenberg, arguing in *favor* of lines in excess of
80
On 8/26/06, Audrey Tang <[EMAIL PROTECTED]> wrote:
Mostly, it's that func('&x' => 1) requires a bit too much typing, and also
makes it hard for func() to change its signature later on to accept things
other than Code.
Allow me to make an immodest proposal. Have named parameter passing
look lik
Mostly, it's that func('&x' => 1) requires a bit too much typing, and also
makes it hard for func() to change its signature later on to accept things
other than Code.
I was discussing this with a friend of mine (Eric Livak), and he suggested
making the sigil on the name optional for disambigua