On Tuesday 23 December 2008 18:47:23 Geoffrey Broadwell wrote:
> On the other hand, I'm somewhat concerned that Parrot 1.0 will either
> itself be rather slow, or will architecturally force HLL implementations
> to be slow. While looking for the IRC discussion mentioned by Coke, I
> found the fol
Strange parsing error:
sub x {
}
while 0 {
my $b = 1;
}
breaks: [[[ Statement not terminated properly at line 6, near "{\n
my $" ]]]
If I add a semicolon after to sub decl, then it's happy:
sub x {
}; ## <--- semicolon here!
while 0 {
my $b = 1;
}
The strange thing is that it's only
On Tue, 2008-12-23 at 17:31 -0800, Will Coleda via RT wrote:
> chromatic mentioned on #parrot that if we remove PIC, we're going to break
> all the
> predereferenced runcores. After some discussion, this probably means ripping
> out:
>
> 16:42 <@chromatic> Everything other than the default core
chromatic via RT wrote:
> On Tuesday 23 December 2008 14:53:15 Jarkko Hietaniemi wrote:
>
>> I am seeing some new warnings, if I find the time I'll file a new bug on
>> those. An easy quick one to fix would be this:
>>
>> cc: Info: ./include/parrot/sub.h, line 47: Trailing comma found in
>> enume
On Tuesday 23 December 2008 14:53:15 Jarkko Hietaniemi wrote:
> I am seeing some new warnings, if I find the time I'll file a new bug on
> those. An easy quick one to fix would be this:
>
> cc: Info: ./include/parrot/sub.h, line 47: Trailing comma found in
> enumerator list. (trailcomma)
> } sub_
chromatic via RT wrote:
> On Wednesday 03 December 2008 18:00:32 Jarkko Hietaniemi wrote:
>
>> First we get a couple of warnings fro some files, but then one file
>> refuses to compile (see below). I didn't notice any other warnings or
>> failures during Configure.pl and/or during compilation.
>
On Thursday 11 December 2008 06:14:36 François PERRAD wrote:
> Since the merge of the branch ppd22io, the mode of the stdin stream has
> changed. Currently, it isn't possible to peek on stdin.
>
> $ cat peek.pir
> .sub 'main'
> $P0 = getstdin
> $S0 = peek $S0
> .end
>
> $
On Wednesday 03 December 2008 18:00:32 Jarkko Hietaniemi wrote:
> First we get a couple of warnings fro some files, but then one file
> refuses to compile (see below). I didn't notice any other warnings or
> failures during Configure.pl and/or during compilation.
Thanks for the report.
> src/op
James Keenan via RT wrote:
On Wed Dec 17 13:29:59 2008, kjs wrote:
I thought I closed it last time. Trying again :-)
kjs
The ticket has 3 dependencies which are still open. Is it possible that
the ticket cannot be resolved until these dependencies are resolved?
Yes, but you can just remove
Patrick R. Michaud via RT wrote:
> On Mon Dec 22 16:41:53 2008, zev wrote:
>> Oops. The last patch wasn't quite right. This one passes the tests
>> (which I found). I also added spectests that are marked TODO (but which
>> pass with this patch applied).
>
> I would prefer to see this done by us
On Mon Dec 22 21:51:05 2008, masak wrote:
> Patrick (>):
> > I would prefer to see this done by using a smart match on the :x()
> > argument instead of explicitly checking it for a Range and grabbing
> > min/max from there. Using a smart match would allow things like
> > :x(1|5|7) and :x({ .is_pri
Patrick R. Michaud via RT wrote:
> On Mon Dec 22 16:41:53 2008, zev wrote:
>> Oops. The last patch wasn't quite right. This one passes the tests
>> (which I found). I also added spectests that are marked TODO (but which
>> pass with this patch applied).
>
> I would prefer to see this done by us
$*ARGS is mentioned in S02/S04 as being the magic filehandle iterator.
However, S06 refers to the "$*ARGS capture." Is there a typo somewhere?
Zev
I was confused about the "Toggle Cc" Javascript link. See RT for the
patch (should these normally be CC'd to p6-compiler?).
Zev
On Mon Dec 22 16:41:53 2008, zev wrote:
> Oops. The last patch wasn't quite right. This one passes the tests
> (which I found). I also added spectests that are mark
On Mon, 22 Dec 2008, Daniel Ruoso wrote:
Em Seg, 2008-12-22 às 15:06 +1100, Timothy S. Nelson escreveu:
On Sat, 20 Dec 2008, Mark Overmeer wrote:
For ???B. In the current set-up, you use CPAN.pm to download, and then
install. The 'cpan' script is a wrapper around CPAN.pm. CPAN.pm starts
the
15 matches
Mail list logo
