[prev in list] [next in list] [prev in thread] [next in thread] 

List:       perl5-porters
Subject:    Re: Clarifying smart match behaviour in when( ... && ... )
From:       "Joshua ben Jore" <twists () gmail ! com>
Date:       2008-02-18 22:40:00
Message-ID: dc5c751d0802181440i44d3dfddg1cff58cd67a35d6d () mail ! gmail ! com
[Download RAW message or body]

On Feb 18, 2008 2:26 PM, brian d foy <brian.d.foy@gmail.com> wrote:
> In article
> <dc5c751d0802181258g6c67410fr42ae86c19571df7e@mail.gmail.com>, Joshua
> ben Jore <twists@gmail.com> wrote:
>
> > On Jan 29, 2008 7:20 PM, brian d foy <brian.d.foy@gmail.com> wrote:
> > > #!/usr/local/bin/perl5.10.0
> >
> > I responded to your use.perl post but here's it for p5p too. You are
> > experiencing a bug. I doubt the implementation is what anyone
> > intended. Here's what's actually happening:
>
> As you pointed out in private email, Perl 5's version shouldl do what
> Perl 6's will do. I've asked on perl6.langauge and I'll wait for Larry
> to make the ruling. I didn't see the answer in S04.
>
> Once I have confirmation that I'm thinking about his right, I'll make a
> doc patch and add more tests (although  I don't think my patch in
> #50538
> was applied yet).

To the extent that any parts of this behavior are likely to change in
Perl 6, I would like Perl 5 to have undefined behavior. If having more
than one element as a target to ~~ or in a when() clause isn't fully
settled, Perl 5 should bail and throw a syntax error.

Josh
[prev in list] [next in list] [prev in thread] [next in thread]