HaloO,
Paul Hodges wrote:
so back to foo("bar"). What's the default behavior? String doesn't Num,
does it? though is does convert if the value is good
I think that Str and Num are disjoint mutually exclusive types.
If you want to get coercive behaviour you need an overloaded
&foo:(Str|Num
在 2006/6/27 下午 4:41 時，Patrick R. Michaud 寫到：
For any who may be interested, my talk slides for
"Perl 6 Compiler Status and the Parrot Compiler Toolkit"
(presented today at YAPC::NA) are available at
http://www.pmichaud.com/2006/pres/yapc-perl6/slide.html
That was a wonderful talk. Thank
I was reading the slides from PM's YAPC::NA, and a thought drifted into
my mind (more of a gentle alarm, actually). One of the examples struck me:
rule parameter_list { [ , ]* }
Its seems common in the higher layers of a grammar that there are more
non-terminal than terminals in each rule, so
On Tue, Jun 27, 2006 at 09:04:27PM -0700, Dave Whipp wrote:
> I was reading the slides from PM's YAPC::NA, and a thought drifted into
> my mind (more of a gentle alarm, actually). One of the examples struck me:
>
> rule parameter_list { [ , ]* }
>
> Its seems common in the higher layers of a g
Looking at Synopsis 12, I notice that the "Enums" section refers to a
"str" type, but Synopsis 6 doesn't, so there is an inconsistency here
that needs correcting.
At first I thought S12 could be updated to use "Str" instead, but
then when looking closer it seemed to me that the enum seemed to
