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()
>>
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
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 this three-way distinction depends on whether a() returns
defined/unde
# New Ticket Created by "Carl Mäsak"
# Please include the string: [perl #58558]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=58558 >
Implement the '...', '???' and '!!!' operators, as described in S03:1691.
Reini Urban wrote:
> for the cygwin070patches branch:
>
> * fix a perlcritic test for Compiler.pm
> * add DESTDIR to languages make install and test-installable
> * fix forth and tcl build/installed seperation and fixed pbc destination paths
> * make builds the default targets, all builds all.
> *
for the cygwin070patches branch:
* fix a perlcritic test for Compiler.pm
* add DESTDIR to languages make install and test-installable
* fix forth and tcl build/installed seperation and fixed pbc destination paths
* make builds the default targets, all builds all.
* fix wrong #ELSEIF to #ELSIF in l
On Wednesday 27 August 2008 07:26:00 Moritz Lenz wrote:
> Carl MXXsak (via RT) wrote:
> > r30589:
> > $ cat for-loop-recursion.bug
> > sub f($l) {
> > return() if $l <= 0;
> > say "entering $l";
> > for 1..3 {
> > f($l-1);
> > say "looping in $l";
> > }
> > }
> > f(2);
On Tue, Sep 2, 2008 at 8:08 AM, François Perrad <[EMAIL PROTECTED]>wrote:
> It seems that PIR uses only one name space of identifiers.
>
> $ cat const.pir
> .const int cst = 42
>
> .sub 'cst'
>print cst
> .end
>
> $ parrot const.pir
> error:imcc:undefined identifier 'cst'
>
>in file 'c
# New Ticket Created by Allison Randal
# Please include the string: [perl #58550]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=58550 >
Deprecate the following vtable functions:
PMC* cmodulus(PMC* value, PMC* dest)
PMC* c
On Wed, Sep 03, 2008 at 03:26:03PM +0200, Carl Mäsak wrote:
> Patrick (>):
> > If both pugs and rakudo agree on an error, I'd bet that the
> > problem is in the program and not the compiler(s). :-)
> >
> > In this case, the problem is the lack of a space before the
> > angle bracket in the loop st
Patrick (>):
> If both pugs and rakudo agree on an error, I'd bet that the
> problem is in the program and not the compiler(s). :-)
>
> In this case, the problem is the lack of a space before the
> angle bracket in the loop statement:
>
>loop (my $i=0;$i<2;$i++) {
>...
>if ($n > 2) { s
On Wed, Sep 03, 2008 at 03:38:29AM -0700, Pim wrote:
> #!/usr/local/bin/pugs -w
>
> loop (my $i=0;$i<2;$i++) {
> say $i;
> }
>
> my $n=7;
> if ($n > 2) { say "$n is bigger than 2";}
> --
> crashes with this error:
> Unexpected "2"
> expecting operator or ";"
> at .
Reini's patch applied as r30719 and Gerd's patch suggestion applied as
r30720. Thanks!
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 test
# New Ticket Created by Pim
# Please include the string: [perl #58544]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=58544 >
Hi,
playing with pugs and parrot compiled perl6 i found this bug:
1st script :
#!/usr/local/
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, s
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; }
On Wednesday 20 August 2008 12:48:27 Reini Urban wrote:
> make dotnet work with the new exceptions.
> I'm not sure how to return the jump_point correctly, but it looks fine.
Thanks, applied as r30718.
-- c
I checked in some major changes that allow all keywords (types and if, null,
etc.) as identifiers. Cleanup and maybe a refactor will follow later.
kjs
On Wed, Sep 3, 2008 at 10:35 AM, Allison Randal <[EMAIL PROTECTED]> wrote:
> Klaas-Jan Stol wrote:
>
>> On Tue, Sep 2, 2008 at 2:28 PM, Allison Ra
Klaas-Jan Stol wrote:
On Tue, Sep 2, 2008 at 2:28 PM, Allison Randal <[EMAIL PROTECTED]> wrote:
I'm not clear on why we need to reserve 'if', 'unless' and 'null' either,
since they never appear in locations that could be confused with variables.
there's not a strict reason, no. In fact, it wo
On Tuesday 08 July 2008 20:56:03 jason switzer wrote:
> When trying to use the --optimize flag, building perl6 causes parrot to
> segfault. Attached is the Configure.pl script output. Below is a backtrace
> by manually performing the make step from gdb. You'll notice the second run
> performs the
Moritz (>), Carl (>>):
>> $ ./perl6 -e 'say =<$*IN>' # doesn't work
>> 0
>
> Shouldn't that be just =$*IN ?
Yes, it should. I claim temporary insanity.
// Carl
On Monday 25 August 2008 08:41:39 Jeff Horwitz wrote:
> rakudo cannot write to %*ENV because the underlying Env PMC apparently
> does not update the environment when using a non-keyed opcode:
The Env PMC is a thin wrapper around setenv(3) and getenv(3). We can change
it to store STRING and PMC
On Sunday 31 August 2008 14:04:53 [EMAIL PROTECTED] wrote:
> +PARROT_API
> +void
> +Parrot_pcc_invoke_sub_from_sig_object(PARROT_INTERP, ARGIN(PMC *sub_obj),
> + ARGIN(PMC *sig_obj))
> +{
> +#define PCC_ARG_MAX 1024
> + /* variables from PCCINVOKE impl in PCCMETHOD.pm */
> + /* args I
24 matches
Mail list logo
