Author: allison
Date: Tue Aug 26 00:52:59 2008
New Revision: 30561
Modified:
trunk/docs/pdds/pdd07_codingstd.pod
Log:
[pdd] Removing credits that are no longer accurate.
Modified: trunk/docs/pdds/pdd07_codingstd.pod
Kevin Tew a écrit :
The merge has happened.
The following patch adds NCIGEN in the documentation (HTML generated).
Note : needs a better title than 'Native Call Interface Generator'.
François.
Developers/Users should see no visible changes.
Please build and test, should you have any problem
On Mon, 25 Aug 2008, Reini Urban wrote:
To clarify my bold statement:
The ALGOL-like syntax is not "sane" because,
* it is hard to parse,
Not actually true. It's just different to parse. And, in general Parrot
optimizes for making code easy to *read* even if it is slightly harder
to parse. We
2008/8/26 Allison Randal <[EMAIL PROTECTED]>:
>> On Mon, 25 Aug 2008, Reini Urban wrote:
>>>
>>> To clarify my bold statement:
>>> The ALGOL-like syntax is not "sane" because,
>>> * it is hard to parse,
>
> Not actually true. It's just different to parse. And, in general Parrot
> optimizes for maki
Author: kjs
Date: Tue Aug 26 04:24:18 2008
New Revision: 30568
Modified:
trunk/docs/pdds/pdd19_pir.pod
Log:
[pdd19] add a comment that PIR keywords cannot be used as PIR identifiers (as
opposed to opcode names, which are allowed).
Modified: trunk/docs/pdds/pdd19_pir.pod
=
Author: kjs
Date: Tue Aug 26 04:27:55 2008
New Revision: 30569
Modified:
trunk/docs/pdds/pdd19_pir.pod
Log:
[pdd19] be a bit more precise in opcode names vs local var names vs sub names.
Modified: trunk/docs/pdds/pdd19_pir.pod
==
Fixed in r30533
# New Ticket Created by Jeff Horwitz
# Please include the string: [perl #58362]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=58362 >
rakudo cannot write to %*ENV because the underlying Env PMC apparently
does not update
Closing ticket
I was wondering ... for problems like these, is there a way to debug what is
going on internally? Is standalone PIR the best way?
Stephen Simmons
On Mon, Aug 25, 2008 at 8:11 AM, Moritz Lenz via RT <
[EMAIL PROTECTED]> wrote:
> Stephen Simmons (via RT) wrote:
> > # New Ticket Created by "Stephe
# New Ticket Created by "Carl Mäsak"
# Please include the string: [perl #58368]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=58368 >
r30537:
$ cat A.pm
use v6;
grammar A {
token b { foo };
};
$ ./perl6 -e 'use A; s
# New Ticket Created by Klaas-Jan Stol
# Please include the string: [perl #58374]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=58374 >
>From PDD19:
Identifiers don't have any limit on length
at the moment, but some sane-
On Tue, Aug 26, 2008 at 7:46 AM, via RT Klaas-Jan Stol
<[EMAIL PROTECTED]> wrote:
> (I think 64 chars. might be enough as well; who's using longer names than
> that?)
As soon as you say 64, you're going to be getting bug reports from
people who want to use 65. This is especially true with all sort
Klaas-Jan Stol (via RT) wrote:
> # New Ticket Created by Klaas-Jan Stol
> # Please include the string: [perl #58374]
> # in the subject line of all future correspondence about this issue.
> # http://rt.perl.org/rt3/Ticket/Display.html?id=58374 >
>
>
> From PDD19:
>
> Identifiers don't have a
Fixed in r30537, closing ticket.
On Monday 25 August 2008, James Keenan via RT wrote:
> On Thu Aug 14 06:03:27 2008, [EMAIL PROTECTED] wrote:
> > On my computer (OpenSuse 11.0) the Parrot Configure.pl hangs forever
> > when
> > checking for platfom support for AIO.
> > It appears to be a neverending sleep(1) loop in the check.
> >
2008/8/25 Allison Randal <[EMAIL PROTECTED]>:
>> (Another way to fix the PDD issues is to eliminate the draft directory
>> and just mark PDDs that are still considered in DRAFT with some
>> decorative POD; that has my vote)
>
> I'm almost done with the PDDs in the draft directory. It's very helpful
# New Ticket Created by "Carl Mäsak"
# Please include the string: [perl #58372]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=58372 >
r30537:
$ ./perl6 -e '$/; say "Alive!"'
get_pmc_keyed() not implemented in class 'Undef'
Done in r30570
Verbose output is now controlled by the 'echo' command. If more debugger
output control is needed, create specific tickets.
On Tue, Aug 26, 2008 at 2:34 AM, Reini Urban <[EMAIL PROTECTED]> wrote:
> I'll go now for something like
>
> #IF(key1|key2&(key3&!key4))
> #IFNOT(key1|key2&(key3&!key4))
>
> And probably a shortcut for the negative else clause, like
> #IF(cygwin):
> #ELSE:
>
> #+ and #- is lisp so I don't want to d
On Mon, Aug 25, 2008 at 10:06 PM, Stephen Simmons
<[EMAIL PROTECTED]> wrote:
> I was wondering ... for problems like these, is there a way to debug what is
> going on internally? Is standalone PIR the best way?
> Stephen Simmons
>
> On Mon, Aug 25, 2008 at 8:11 AM, Moritz Lenz via RT <
> [EMAIL PR
I have noticed that Rakudo (and NQP) generates different PIR code for
implicit and explicit returns.
Example for implicit return:
sub foo($n){
$n;
}
And example for explicit return:
sub foo($n){
return $n;
}
Is this on purpose? The implicit return is 4-5 times faster than
explicit re
On Tue, Aug 26, 2008 at 10:53 AM, luben <[EMAIL PROTECTED]> wrote:
> I have noticed that Rakudo (and NQP) generates different PIR code for
> implicit and explicit returns.
>
> Example for implicit return:
>
> sub foo($n){
> $n;
> }
>
> And example for explicit return:
>
> sub foo($n){
> return
On Tue, Aug 26, 2008 at 01:28:22AM -0700, Carl Mäsak wrote:
> r30537:
> $ ./perl6 -e '$/; say "Alive!"'
> get_pmc_keyed() not implemented in class 'Undef'
> [...]
>
> Compare Perl 5:
>
> $ perl -Mstrict -we '$_{'a'}{'b'}; print "Alive!\n"'
> Useless use of hash element in void context at -e line
Patrick R. Michaud wrote:
> On Tue, Aug 26, 2008 at 01:28:22AM -0700, Carl Mäsak wrote:
>> r30537:
>> $ ./perl6 -e '$/; say "Alive!"'
>> get_pmc_keyed() not implemented in class 'Undef'
>> [...]
>>
>> Compare Perl 5:
>>
>> $ perl -Mstrict -we '$_{'a'}{'b'}; print "Alive!\n"'
>> Useless use of has
jerry gay schrieb:
On Tue, Aug 26, 2008 at 2:34 AM, Reini Urban <[EMAIL PROTECTED]> wrote:
I'll go now for something like
#IF(key1|key2&(key3&!key4))
#IFNOT(key1|key2&(key3&!key4))
I went for #UNLESS(expr): here.
Also #ELSIF(expr):
And probably a shortcut for the negative else clause, like
On Tue, Aug 26, 2008 at 9:16 AM, Reini Urban <[EMAIL PROTECTED]> wrote:
> jerry gay schrieb:
>>
>> On Tue, Aug 26, 2008 at 2:34 AM, Reini Urban <[EMAIL PROTECTED]> wrote:
>>>
>>> I'll go now for something like
>>>
>>> #IF(key1|key2&(key3&!key4))
>>> #IFNOT(key1|key2&(key3&!key4))
>
> I went for #UN
On Tuesday 26 August 2008 00:16:10 [EMAIL PROTECTED] wrote:
> Log:
> [pipp] more freed and PIR'd phparray tests
> --- trunk/languages/pipp/t/pmc/array.t(original)
> +++ trunk/languages/pipp/t/pmc/array.tTue Aug 26 00:16:09 2008
> @@ -562,9 +567,296 @@
> is_ok = 0
> current_a
On Tue Aug 26 06:15:19 2008, [EMAIL PROTECTED] wrote:
> On Monday 25 August 2008, James Keenan via RT wrote:
> >
> > 1. After you run 'perl Configure.pl' with this patch on your box,
> what
> > do you get for this:
> >
> > grep -ni AIO lib/Parrot/Config/Generated.pm
>
> AIO is not in the file.
On Tuesday 26 August 2008 06:13:07 [EMAIL PROTECTED] wrote:
> --- trunk/compilers/pirc/new/pircompunit.c (original)
> +++ trunk/compilers/pirc/new/pircompunit.c Tue Aug 26 06:13:06 2008
> @@ -24,6 +24,29 @@
> of the parsed PIR code. Through the symbol management, which is done
> in F,
jerry gay wrote:
#+ and #- is lisp so I don't want to destroy #+ the syntax rules.
#IF(): is quite short and easy to read.
i know it was all caps before, but do we need to continue that trend?
i find it ugly.
All-caps is the Parrot coding standard for macros and #defines, and
these fall in
jerry gay wrote:
On Tue, Aug 26, 2008 at 9:16 AM, Reini Urban <[EMAIL PROTECTED]> wrote:
jerry gay schrieb:
On Tue, Aug 26, 2008 at 2:34 AM, Reini Urban <[EMAIL PROTECTED]> wrote:
I'll go now for something like
#IF(key1|key2&(key3&!key4))
To make sure, that means basically the same thing as
On Tue, Aug 26, 2008 at 11:00 AM, Allison Randal <[EMAIL PROTECTED]> wrote:
> jerry gay wrote:
>>>
>>> #+ and #- is lisp so I don't want to destroy #+ the syntax rules.
>>> #IF(): is quite short and easy to read.
>>>
>> i know it was all caps before, but do we need to continue that trend?
>> i find
Remove the Makefile target and remove commented section
from the root makefile.
Add cardinal.install to languages.in
Rename LANG to TMPL in all language makefiles.
Conflicts with perl urmc locale.
The new compiler not yet.
--
Reini Urban
http://phpwiki.org
Will Coleda wrote:
On Tue, Aug 26, 2008 at 10:53 AM, luben <[EMAIL PROTECTED]> wrote:
I have noticed that Rakudo (and NQP) generates different PIR code for
implicit and explicit returns.
Example for implicit return:
sub foo($n){
$n;
}
And example for explicit return:
sub foo($n){
return
On Tue, 26 Aug 2008, luben wrote:
I have noticed that Rakudo (and NQP) generates different PIR code for
implicit and explicit returns.
Example for implicit return:
sub foo($n){
$n;
}
And example for explicit return:
sub foo($n){
return $n;
}
Is this on purpose? The implicit return is
Will Coleda wrote:
On Tue, Aug 26, 2008 at 10:53 AM, luben <[EMAIL PROTECTED]> wrote:
Is this on purpose? The implicit return is 4-5 times faster than explicit
return.
Best regards
luben
CC'ing perl6-compiler (where rakudo-particular items should go), and
wondering if you can attach the gene
Jeff Horwitz wrote:
the implicit return is by definition always at the end of a sub and
therefore emits a PIR .return(). it's fast and easy.
the explicit return, in contrast, could be anywhere in a subroutine,
including loops, closures, etc. these constructs are also implemented
using parro
On Tue, Aug 26, 2008 at 11:42:51PM +0300, luben karavelov wrote:
> I can run the NQP generated PIR after addition of:
>
> load_bytecode 'compilers/nqp/nqp.pbc'
>
> in the first sub. But I can not find how to run rakudo generated PIR
> code. The "load_bytecode" seems no be not enought (some months
From: Klaas-Jan Stol (via RT) <[EMAIL PROTECTED]>
Date: Tue, 26 Aug 2008 04:46:56 -0700
From PDD19:
Identifiers don't have any limit on length at the moment, but some
sane-but-generous length limit may be imposed in the future (256
chars, 1024 chars?).
If the code already suppo
Patched two subs in Parrot::Configure and adjusted test files in r30583.
Tested with triggers in hints files on Linux and Darwin.
Thank you very much.
kid51
OK, here's my straw-man proposal for a language interoperability
framework; my apologies for sitting on it so long. It's still pretty
messy, but I'm sure it will benefit more from other viewpoints at this
stage than from polishing.
-- Bob Rogers
James Keenan via RT wrote:
On Mon Aug 25 13:15:16 2008, [EMAIL PROTECTED] wrote:
Generally recommend attaching patches as files ending in .patch (as
documented in docs/submissions.pod) for the sanity of the patch
monsters.
Well, since it's in the docs, I will withdraw the suggestion.
Howev
44 matches
Mail list logo
