HaloO,
I have one further question to the document. It mentions
chains of type coercions that are applied in the compatibility
stage. A type that has fewer conversion steps is considered
more specific. But is that a wise thing to do in an MMD system?
I would expect no coercions to occur. How can
Author: audreyt
Date: Thu Nov 2 03:23:56 2006
New Revision: 13379
Modified:
doc/trunk/design/syn/S03.pod
Log:
* S03: Explicitly mention .=meth in the term level.
* Also explicitly mention that the implicit topic for
.meth and .=meth is $_.
Modified: doc/trunk/design/syn/S03.pod
==
Author: audreyt
Date: Thu Nov 2 03:00:10 2006
New Revision: 13377
Modified:
doc/trunk/design/syn/S03.pod
doc/trunk/design/syn/S06.pod
Log:
* S03: Missing semicolon.
* S06: Missing comma. (spotted by cognominal++.)
Modified: doc/trunk/design/syn/S03.pod
HaloO,
Audrey Tang wrote:
> A variant's score cards only records two Boolean values for each
> variant: "voting" and "qualified".
Here is a summary of the explanation Audrey gave me on #perl6.
Note that this is from memory because I didn't save the log.
In particular I don't remember exactly whe
