yada yada yada in regex

2008-06-08 Thread Stéphane Payrard
what is the equivalent convention for yadayadayada in regex. Cuz ... is alread meaningful in regex. Should I use ... or {...} ? Should the first be predefined? I want something that is a placeholder that parses but fails if someone pastes it. In other words the equivalent of a sub yada yada

Foo.HOW.metamethod vs Foo.^metamethod

2008-06-08 Thread Daniel Ruoso
Hi, When implementing prototype OO, the HOW for objects with different behaviours will be shared. This issue is not new, but before we thought that it would be possible to solve that by forcing $foo.HOW to be a proxy object that would rewrite the call putting $foo as the invocant. Me and

Re: yada yada yada in regex

2008-06-08 Thread Daniel Ruoso
Sáb, 2008-06-07 às 16:01 +0200, Stéphane Payrard escreveu: what is the equivalent convention for yadayadayada in regex. Cuz ... is alread meaningful in regex. Should I use ... or {...} ? Should the first be predefined? If I understand correctly, {...} should already be parsed as a yada yada

clarification on samecase() and samebase()

2008-06-08 Thread Moritz Lenz
Hi all, Auzon has written a few tests for the samecase() and samebase() (S29), which raised a question: For both the :samecase and there :samebase regex modifier (S05) there is a dumb and a smart version. S29 is silent about which it refers to. Should both have a second, optional argument which

Re: Fatal/autodie exception hierarchies for Perl 5

2008-06-08 Thread Joshua ben Jore
On Sun, Jun 1, 2008 at 7:31 PM, Paul Fenwick [EMAIL PROTECTED] wrote: Currently, when testing exceptions from autodie, we can use: given ($@) { when (undef) { say No errors here } when ('open') { say Open died } when (':file') { say Some

Re: Fatal/autodie exception hierarchies for Perl 5

2008-06-08 Thread Paul Fenwick
G'day Josh / p5p / p6l, given ($@) { # [snip] default{ say Not an autodie exception. } } If you're going to write that into some documentation, I wish you'd make default say that it's exception suicide. The documentation clearly needs