On Tue, 2008-09-02 at 12:32 -0700, Darren Duncan wrote:
Now a common factor to both of my proposals is that this Test.pm is
intentionally kept as simple as possible and contains just the
functionality needed to bootstrap the official Perl 6 test suite; if the
official test suite doesn't use
While S02 reserves some all caps names, I assume that all lower case class
names are okay (I don't see anything against them). Rakudo doesn't support
them. Is this a bug or is there something in the synopsis that I've missed.
Here is my example:
class Test { has $.x; }
class test { has $.x; }
Hi,
Stephen Simmons wrote:
While S02 reserves some all caps names, I assume that all lower case class
names are okay (I don't see anything against them). Rakudo doesn't support
them.
This is a not yet implemented feature. Basically Rakudo doesn't keep a
symbol table yet while parsing, so it
Two sorts of testing - a) compiler, b) modules.
Each category has different environment and function.
a) compiler.
An official test suite is defined (and probably will be added to as
corner cases / ambiguities are discovered and disambiguation decided, so
presumably some standardisation of
I'm trying to work out some details of this area, but I don't understand what S04 is
trying to say. Could someone please point me in the right direction? I'd be happy to
then edit the S04 to contribute.
In S04, the Exceptions section mentions that $! contains multiple exceptions.
So what
On Wed, Sep 03, 2008 at 06:41:10PM -0500, John M. Dlugosz wrote:
Larry Wall larry-at-wall.org |Perl 6| wrote:
a() orelse b()
you might want to:
succeed on a()
trap mild failure of a() and try to succeed on b() instead
fail completely on drastic failure of a()
At the moment
