From: "NotFound via RT" <[EMAIL PROTECTED]>
Date: Tue, 09 Sep 2008 10:47:05 -0700
I've recently commited a fix on null string constants. I think it was
the same problem described here. I compiled the pir file and pdumped
without a problem, it shows the DATA => NULL my fix introduced
On Tue Sep 09 18:22:30 2008, [EMAIL PROTECTED] wrote:
>
> I extracted the attached patch from email text and applied it in r30946.
For some reason, the first attachment -- Andy's patch -- didn't get
attached. Trying again.
diff -r -u parrot-current/config/auto/aio/aio.in
parrot-andy/config/au
From: Bob Rogers (via RT) <[EMAIL PROTECTED]>
Date: Sun, 07 Sep 2008 18:52:40 -0700
# New Ticket Created by Bob Rogers
# Please include the string: [perl #58660]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?
On Tue Sep 09 15:14:36 2008, [EMAIL PROTECTED] wrote:
>
> Generally agreed. In this case, hold this ticket for the I/O milestone,
> which is next (sometime in the next few days). I've added it to the I/O
> tasklist.
>
> In the meantime, let's get Andy's patch applied (if it isn't already).
>
James E Keenan wrote:
This post is addressed to those of you who (a) have Perl 5 programming
skills and (b) have been lurking on the list or on #parrot without yet
dipping your toes in the water.
I have a number of projects, some of which are already in the form of RT
tickets, some not, which
On Sun Sep 07 15:19:22 2008, cotto wrote:
> On Thu Jun 12 10:23:06 2008, [EMAIL PROTECTED] wrote:
> > On Thursday 12 June 2008 10:01:21 NotFound wrote:
> >
> > > Some more details: adding:
> > >
> > > Parrot_set_flag(interp, PARROT_DESTROY_FLAG);
> > >
> > > in src/main.c it segfaults also when ex
On Tuesday 09 September 2008 11:07:09 [EMAIL PROTECTED] (via RT) wrote:
> I attached a tar-file that holds one patch file (generated with diff -u)
> for each modified file.
This makes patches very difficult to review; can you send a single patch file
instead?
-- c
Ter, 2008-09-09 às 10:10 -0500, Patrick R. Michaud escreveu:
> I think my question can be best understood by example -- what
> does the following produce?
> my @a = 1,2,3,4,5;
> for @a { .say; @a = (); }
The problem actually becomes more evident with
my @a = 1,2,3,4,5;
for @a { .say;
# New Ticket Created by [EMAIL PROTECTED]
# Please include the string: [perl #58726]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=58726 >
Hello,
this patch adds the option "encoding" to the configuration of Parrot:
> pe
> This falls under the I/O PDD, the next milestone. Hold for a couple of
> days. I've added it to the tasklist for the milestone:
The print and say opcodes had already been changed some weeks ago, now
both call PIO_printf on INT and NUM.
By the way, now FLOATVAL_FMT is used instead of "%f"
I've recently commited a fix on null string constants. I think it was
the same problem described here. I compiled the pir file and pdumped
without a problem, it shows the DATA => NULL my fix introduced.
Can you verify the problem is gone?
With this commit r30847, partcl & lua are broken.
$ ./parrot languages/lua/lua.pbc
Segmentation fault
#0 0xb7c93a03 in pmc_new_noinit (interp=0x804f040, base_type=86) at
src/pmc.c:300
#1 0xb7c4dd5b in Parrot_register_HLL_type (interp=0x804f040, hll_id=1,
core_type=17, hll_type=86) at src/hll.c:
> >rakudo: sub foo($x?, :$y = 2){ say "$x"~"|"~"$y"}; foo(:y(3));
> >exp_evalbot
> >OUTPUT[|]
>
> This appears to be a bug in Parrot (now RT#54860). When that's fixed
> this one should be fixed also.
RT#54860 is fixed, verified:
rakudo: sub foo($x?, :$y = 2){ say "$x"~"
TSa Thomas.Sandlass-at-vts-systems.de |Perl 6| wrote:
Since Larry said that single assignment semantics is the ideal
we should strive for, I would opt for the iterator being unaffected
by the assignment to @a. When this happens the singly assigned
former content of @a is snaphot by the iterator.
My take on it:
The 'for' loop does bind $_ to alias each item of the list in turn.
But, "the list" is not synonymous with the variable named @a. However,
the = operator operates on "the list" itself, not the container,
replacing the elements in the existing Array (or whatever) object. So,
On Tuesday 09 September 2008 15:34:21 [EMAIL PROTECTED] wrote:
> [pdd27mmd] Fix failing coding standards test for line length.
>
>
> Modified: branches/pdd27mmd/src/multidispatch.c
> ===
>=== --- branches/pdd27mmd/src/multidis
Will Coleda wrote:
Instead of spending time fixing a probe that isn't being used, we
should rip it out. If we eventually need it again, we can start from
here, but there's no point in probing for features that we never use.
It's wasting developer (and less importantly, CPU) time better spent
els
Patrick R. Michaud wrote:
Just for clarification: IIUC, the n_* opcodes and their semantics
aren't really "going away" -- they're simply being renamed to not
have the leading "n_" prefix. It's the existing "add", "sub",
"mul", "div", etc. opcodes that are being eliminated.
Yes. That is, c
chromatic wrote:
t/op/calling_61.pir crashes because Parrot's trying to treat the number -1 as
a PMC. Why?
The desired MMD sub should take two PMCs and returns an INTVAL (frame #5,
signature "PP->I"), but the invoked MMD sub takes two PMCs and returns a PMC.
The crash comes in convert_arg,
Google has graciously agreed to host the first ever Parrot Developer
Summit. November 15th and 16th, 2008 on Google's Mountain View campus.
You can find directions to the campus at:
http://code.google.com/events/visitors
More details to follow. Hope to see you there!
Allison
t/op/calling_61.pir crashes because Parrot's trying to treat the number -1 as
a PMC. Why?
Parrot_convert_arg (interp=0x804f040, st=0xbf8b70c0) at src/inter_call.c:905
905 if (key->vtable->base_type != enum_class_Key)
(gdb) bt
#0 Parrot_convert_arg (interp=0x804f040, st=0xbf8b70c0)
a
Michael Peters wrote:
> Moritz Lenz wrote:
>
>> the graphs on http://smolder.plusthree.com/app/public_graphs/start/8
>> become pretty useless as soon as I select a larger time span (say, 5
>> days): instead of displaying data, it mostly displays a gray area of
>> fancy 3D shadows.
>
> I agree tha
Moritz Lenz wrote:
the graphs on http://smolder.plusthree.com/app/public_graphs/start/8
become pretty useless as soon as I select a larger time span (say, 5
days): instead of displaying data, it mostly displays a gray area of
fancy 3D shadows.
I agree that the shadows can cause a problem. But
Hi,
the graphs on http://smolder.plusthree.com/app/public_graphs/start/8
become pretty useless as soon as I select a larger time span (say, 5
days): instead of displaying data, it mostly displays a gray area of
fancy 3D shadows.
Maybe the graph generation could be tweaked, or a simple, traditiona
Will Coleda (via RT) wrote:
> # New Ticket Created by Will Coleda
> # Please include the string: [perl #58724]
> # in the subject line of all future correspondence about this issue.
> # http://rt.perl.org/rt3/Ticket/Display.html?id=58724 >
>
>
> http://smolder.plusthree.com/app/public_project
# New Ticket Created by Will Coleda
# Please include the string: [perl #58724]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=58724 >
http://smolder.plusthree.com/app/public_projects/report_details/5297#first_failure
(but
On Tuesday 09 September 2008 09:51:37 Allison Randal wrote:
> jerry gay wrote:
> > can they be replaced by roles?
> Potentially, yes. In the case of the scalar PMC it would make quite a
> bit of sense as a role (composing in behavior common to scalar data
> types). For the default PMC it makes l
jerry gay wrote:
On Mon, Sep 8, 2008 at 1:09 AM, Allison Randal <[EMAIL PROTECTED]> wrote:
a) Do abstract base classes as currently implemented in Parrot serve any
useful purpose? If not, eliminate them.
can they be replaced by roles?
Potentially, yes. In the case of the scalar PMC it would
> I put the commands that I'm using in the README file (but that's for MSVC on
> windows), but I don't have any knowledge on how to do this on linux.
There is no README file in compilers/pirc/new
--
Salu2
HaloO,
Patrick R. Michaud wrote:
My question is whether the change to @a inside the for loop
affects the iterator created at the beginning of the for loop.
Since Larry said that single assignment semantics is the ideal
we should strive for, I would opt for the iterator being unaffected
by the
On Tue, Sep 09, 2008 at 10:10:04AM -0500, Patrick R. Michaud wrote:
: I think my question can be best understood by example -- what
: does the following produce?
:
: my @a = 1,2,3,4,5;
: for @a { .say; @a = (); }
:
: My question is whether the change to @a inside the for loop
: affects th
HaloO,
Jon Lang wrote:
Actually, note that both infix:<,> and circumfix:<[ ]> can be used to
build lists; so [1] and [] can be used to construct single-element and
empty lists, respectively.
I doubt that. Actually, circumfix:<[ ]> builds arrays. And note that
there's no infix operator that con
hi,
recently I had a good look at Parrot's Makefile to figure out what link
flags I need to link PIRC against libparrot.
This worked out quite well, and I'm now able to link in libparrot so PIRC
can now call all Parrot functions.
(the only major thing that needs to be done to get rid of IMCC is gen
Patch rejected; the patch appears to eliminate "Perl6Scalar"
entirely from the 'is copy' semantics, this means we'd be without
an appropriate Scalar container for something like
sub foo($a is copy) { ... }
In general I think much of the signature handling in Rakudo needs
a significant refact
I think my question can be best understood by example -- what
does the following produce?
my @a = 1,2,3,4,5;
for @a { .say; @a = (); }
My question is whether the change to @a inside the for loop
affects the iterator created at the beginning of the for loop.
In other words, would the above
On Tue Sep 09 05:57:40 2008, coke wrote:
> On Tue, Sep 9, 2008 at 8:46 AM, Andy Dougherty
> <[EMAIL PROTECTED]> wrote:
> > Parrot's also not using AIO anywhere either, so the whole probe is
> kind of
> > pointless right now.
>
> Instead of spending time fixing a probe that isn't being used, we
> s
# New Ticket Created by Vasily Chekalkin
# Please include the string: [perl #58718]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=58718 >
Hello.
During investigating bug from #58276 I found very nasty bug with
assigning
Hello.
There is patch that fixes this error (and makes first 6 tests from
S06/slurpy-params.t passing). Unfortunately it triggers bug from #58718
--
Bacek.
diff --git a/languages/perl6/src/parser/actions.pm b/languages/perl6/src/parser/actions.pm
index 349f433..27ddcd0 100644
--- a/languages/per
perl6 via RT wrote:
During investigating bug from #58276 I found very nasty bug with
assigning to Perl6Scalar.
Actually bug #58278.
--
Bacek
Patrick R. Michaud via RT wrote:
For Rakudo and other PCT-related items we should generally not
be using the 'new' opcode to create objects. The correct
approach is
## $P1 = Range.new;
$P0 = get_hll_global 'Range'
$P1 = $P0.'new'()
Ok, but List is definetely wrong:
.sub "main"
On Tue, 9 Sep 2008, Will Coleda wrote:
> On Tue, Sep 9, 2008 at 8:46 AM, Andy Dougherty <[EMAIL PROTECTED]> wrote:
> > Parrot's also not using AIO anywhere either, so the whole probe is kind of
> > pointless right now.
>
> Instead of spending time fixing a probe that isn't being used, we
> should
It seems that the error condition refers to the case where too many
arguments are passed (#args > #params).It's not really "overflow" in that
sense, IMHO, just "too many arguments passed".
I think an exception is already thrown when that happens, not sure.
kjs
On Tue, Sep 9, 2008 at 12:02 AM, c
On Fri, Sep 05, 2008 at 05:20:45PM -0700, Christoph Otto via RT wrote:
> > On Tue, May 13, 2008 at 9:48 AM, via RT Patrick R. Michaud
> > > The infix and n_infix opcodes cause segfaults when invoked with
> > > string arguments. (Kubuntu 8.04, x86, r27472)
> > > $ cat z.pir
> > > .sub main :mai
Tim Heckman wrote:
> NotFound wrote:
>> On Tue, Sep 9, 2008 at 5:23 AM, via RT Tim Heckman
>> <[EMAIL PROTECTED]> wrote:
>>
>>> # New Ticket Created by "Tim Heckman"
>>> # Please include the string: [perl #58704]
>>> # in the subject line of all future correspondence about this issue.
>>> # htt
On Tue, Sep 9, 2008 at 8:46 AM, Andy Dougherty <[EMAIL PROTECTED]> wrote:
> Parrot's also not using AIO anywhere either, so the whole probe is kind of
> pointless right now.
Instead of spending time fixing a probe that isn't being used, we
should rip it out. If we eventually need it again, we can
On Tue, Sep 09, 2008 at 08:46:33AM -0400, Andy Dougherty wrote:
> Parrot's also not using AIO anywhere either, so the whole probe is kind of
> pointless right now. Mainly, I was just hoping that a minor fix would
> help solve Patrick's problem of Configure.pl hanging during the aio probe.
> I
On Sat, 6 Sep 2008, chromatic wrote:
> On Saturday 06 September 2008 20:19:56 James Keenan via RT wrote:
>
> test_17787.c: In function 'main':
> test_17787.c:45: error: 'SIGRTMIN' undeclared (first use in this function)
> test_17787.c:45: error: (Each undeclared identifier is reported only once
NotFound wrote:
On Tue, Sep 9, 2008 at 5:23 AM, via RT Tim Heckman
<[EMAIL PROTECTED]> wrote:
# New Ticket Created by "Tim Heckman"
# Please include the string: [perl #58704]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id
On Tue Nov 20 20:58:35 2007, [EMAIL PROTECTED] wrote:
> On Wed Mar 14 07:49:33 2007, [EMAIL PROTECTED] wrote:
> > Hi,
> >
> > Given the following:
> >
> > .namespace ['A']
> >
> > .sub 'morph' :method :vtable
> > say 'morphing!'
> > .end
> >
> > .sub main :main
> > $P0 = newclass 'A'
>
On Tue, Sep 9, 2008 at 5:23 AM, via RT Tim Heckman
<[EMAIL PROTECTED]> wrote:
> # New Ticket Created by "Tim Heckman"
> # Please include the string: [perl #58704]
> # in the subject line of all future correspondence about this issue.
> # http://rt.perl.org/rt3/Ticket/Display.html?id=58704 >
> li
# New Ticket Created by "Tim Heckman"
# Please include the string: [perl #58704]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=58704 >
Output of prove -v t\src\compiler.t is attached.
The generated linker command is incor
On Mon Mar 19 10:22:42 2007, coke wrote:
> test TODOd for next release, thanks for the report.
>
> (Hopefully it'll get fixed shortly after the release.)
>
> On Sun Mar 18 08:07:05 2007, [EMAIL PROTECTED] wrote:
> > I get SIGSEGV in t/stm/llqueue, test #2
> >
> > openSuSe 10.2 linux 2.6.18.8-0.
52 matches
Mail list logo
