# New Ticket Created by Patrick R. Michaud
# Please include the string: [perl #48467]
# in the subject line of all future correspondence about this issue.
# URL: http://rt.perl.org/rt3/Ticket/Display.html?id=48467
Using assign with an Object causes it to create a Ref
instead of assigning a
Andy Armstrong wrote:
Again, let me know if you need more.
I pushed it far enough that I was able to repeat the deadlock hang on OS
10.4.11, that's good. The interesting thing was the order of operations.
The usual order is:
call to Parrot_cx_init_scheduler
initializing scheduler runloop
On Dec 11, 2007 8:43 AM, Joshua Isom [EMAIL PROTECTED] wrote:
On Dec 10, 2007, at 10:59 AM, Klaas-Jan Stol wrote:
In order to draw attention to this point, I changed the subject.
Is there anybody who thinks the removal from PIR of $-less registers
(absolute or PASM registers) should
Andy Armstrong wrote:
Where might a volunteer start?
I also promised Yuval that I'd refactor Test::TAP::Model to use
Test::Harness 3.00 - so to some extent I've answered my own question -
but I'd like to get my hands dirty with Parrot proper too.
There's a tricky spot at the very beginning
On Dec 11, 2007 8:43 AM, Joshua Isom [EMAIL PROTECTED]
Parrot provides a calling convention, but does not, that I know of,
mandate that calling convention. In any computer, there are multiple
calling conventions used(often leading to a lack of interoperability,
but nevertheless
On 11 Dec 2007, at 04:57, Randal L. Schwartz wrote:
Andy == Andy Armstrong [EMAIL PROTECTED] writes:
Andy Rubinus (new Ruby runtime)
Andy http://www.infoq.com/news/2007/12/engine-yard-bets-big-rubinius
I'm trying to figure out why Rubinous is building a squeak-like vm
when squeak already has
On Mon, 10 Dec 2007, James Keenan wrote:
The patch attached proposes to refactor Parrot configuration step
class inter::progs into two classes: inter::compiler and inter::progs.
inter::compiler will search for a C compiler, process any --cc option
set on the command line and, if
From: Andy Dougherty via RT
Date: 2007/12/11 Tue AM 08:38:17 CST
Subject: Re: [perl #48459] [PATCH]: Refactor config/inter/progs.pm into 2
config steps
I don't think this will work. Specifically, to conduct a basic test of
that compiler's functioning you need to compile *and link* a
Andy == Andy Armstrong [EMAIL PROTECTED] writes:
Andy Or perhaps somebody could podcast an interview with them? :)
Perhaps you were joking, but I noted that as a potential show for FLOSS
Weekly. Thanks for the idea.
--
Randal L. Schwartz - Stonehenge Consulting Services, Inc. - +1 503 777
On 11 Dec 2007, at 17:28, Randal L. Schwartz wrote:
Andy == Andy Armstrong [EMAIL PROTECTED] writes:
Andy Or perhaps somebody could podcast an interview with them? :)
Perhaps you were joking, but I noted that as a potential show for
FLOSS
Weekly. Thanks for the idea.
Not joking just
On Tuesday 11 December 2007 03:58:38 Andy Armstrong wrote:
It'd be interesting to get all these folk who are working on VMs
around a table to chat about their respective rationales.
That may happen in early February. It did happen for a bit at Foo Camp this
summer.
Or perhaps somebody
On Tue, 11 Dec 2007, Jim Keenan wrote:
From: Andy Dougherty via RT
Date: 2007/12/11 Tue AM 08:38:17 CST
Subject: Re: [perl #48459] [PATCH]: Refactor config/inter/progs.pm into 2
config steps
I don't think this will work. Specifically, to conduct a basic test of
that compiler's
Task description:
Add an opcode 'copy' to src/ops/set.ops. Similar to 'clone'.
- It takes two PMC arguments
- It calls VTABLE_morph on $1, and then VTABLE_assign on the two.
- It needs to call VTABLE_type to get the type of the source PMC to pass
to 'morph' instead of calling
The reports of find_name's death are greatly exaggerated. Rejecting ticket.
Pm
On 11 Dec 2007, at 09:20, Allison Randal wrote:
Coding is just a little bit zen. Programmer who can catch a fly
with chopsticks can accomplish anything.
Nah, I couldn't possibly code while I was running around trying to hit
a fly with a stick :)
I guess once I get some headspace I'll
On 11 Dec 2007, at 22:39, Tim Bunce wrote:
Perhaps new contributors could make notes about stumblings blocks
encountered along the way, so we know where to put signposts for
others
who follow.
Good plan. I'll keep notes.
--
Andy Armstrong, Hexten
On Mon, 10 Dec 2007, James Keenan wrote:
The patch attached proposes to refactor Parrot configuration step
class inter::progs into two classes: inter::compiler and inter::progs.
Are we at any risk of redoing work here? Other OSS projects must
presumably have faced the same problems. How do
On Tue, Dec 11, 2007 at 11:20:39AM +0200, Allison Randal wrote:
Andy Armstrong wrote:
Where might a volunteer start?
I also promised Yuval that I'd refactor Test::TAP::Model to use
Test::Harness 3.00 - so to some extent I've answered my own question - but
I'd like to get my hands dirty
Steve Peters' posting didn't make it to RT, so I'm excerpting it here.
[EMAIL PROTECTED] wrote:
hints/linux.pm should really have separate flags for even g++, since
some warnings just don't work on g++.
I think it would be good if we could break out compilers separately
from the operating
Resolved by withdrawal.
# New Ticket Created by James Keenan
# Please include the string: [perl #48493]
# in the subject line of all future correspondence about this issue.
# URL: http://rt.perl.org/rt3/Ticket/Display.html?id=48493
Pursuant to discussion between Andy Dougherty and myself in http://
# New Ticket Created by Will Coleda
# Please include the string: [perl #48495]
# in the subject line of all future correspondence about this issue.
# URL: http://rt.perl.org/rt3/Ticket/Display.html?id=48495
... and should be in the src/ directory.
It's referenced in a lot of places (docs,
# New Ticket Created by Will Coleda
# Please include the string: [perl #48497]
# in the subject line of all future correspondence about this issue.
# URL: http://rt.perl.org/rt3/Ticket/Display.html?id=48497
When building parrot, we get the following warning:
setstdout_p
On Dec 11, 2007 12:40 PM, Andy Dougherty [EMAIL PROTECTED] wrote:
On Tue, 11 Dec 2007, Jim Keenan wrote:
From: Andy Dougherty via RT
Date: 2007/12/11 Tue AM 08:38:17 CST
Subject: Re: [perl #48459] [PATCH]: Refactor config/inter/progs.pm into
2 config steps
I don't think this
Now that I've got all but one function headerized, I'm running splint.
One of the things that splint is good at, and the reason I did all the
PARROT_CAN(NOT)_RETUN_NULL flags, is it'll keep track of when something
could be NULL or not. So splint complains here:
char * const p = malloc(n);
p-foo
On Tue Dec 11 10:41:18 2007, doughera wrote:
[snip]
I think you're missing three things:
cc_build() consults the global $conf, and hence doesn't need it passed
in.
I would certainly agree that the flow of information isn't well
controlled
here. Passing the object in sometimes and other
From: Allison Randal [EMAIL PROTECTED]
Date: Tue, 11 Dec 2007 11:51:52 +0200
The thing is, PIR doesn't respect the register numbers anyway (even in
the so-called absolute registers). So P33 in the PIR source may
compile down to P0, and P0 in the PIR source may compile down to
# New Ticket Created by Patrick R. Michaud
# Please include the string: [perl #48507]
# in the subject line of all future correspondence about this issue.
# URL: http://rt.perl.org/rt3/Ticket/Display.html?id=48507
The n_add, n_sub, etc. opcodes don't seem to work when an object
is used as
Tonight I've been working on getting the headerizer to automagically
update the comment blocks for each function in a .c file (.pmc files
will come later). The goal here is twofold:
1) The documentation is always consistent, because the declaration-
based documentation is
29 matches
Mail list logo
