On Mar 9, 2007, at 10:42 AM, Will Coleda via RT wrote:
On Mon Mar 05 16:57:47 2007, [EMAIL PROTECTED] wrote:
Two months ago, I filed this bug report (excerpt):
I'm still not seeing the effects of the bug you describe, btw. (on
OS X
intel or ppc). It does remind me of issues I had when atte
Following conversation with Matt Diephouse on #parrot, I realized that
that was pretty confusing. What I meant was that invoke() should
accept parameters and return values as a normal subroutine. This
would probably be done by moving the code that deals with the pc out
of the invoke() method and
That is definitely the most elegant solution. Now, the question is, shouldn't
the invoke() vtable method behave that way in the first place, since passing a
pc address to and returning another pc address from the invoke() method only
makes sense for Sub, Coroutine, and Continuation? In other
- Y Y YY ?
20070116
linux-x86_64-gcc4.1.0 4 Y-- Y Y YY/2 ?
20060807
linux-x86_64-gcc4.1.2 8 Y-- Y Y YY ?
20070116
+openbsd-zaurus-gcc3.3.5 Y-- Y Y Y? ?
20070309
sol8-sp
# New Ticket Created by Will Coleda
# Please include the string: [perl #41768]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=41768 >
Begin forwarded message:
> From: Klaas-Jan Stol <[EMAIL PROTECTED]>
> Date: March 9, 2
chromatic wrote:
On Friday 09 March 2007 05:00, Ron Blaschke wrote:
Attached patch replaces the backslashes with slashes on Windows.
Would using File::Spec be less fragile?
The problem basically boils down to matching a list of MANIFEST (UNIX?)
files with the (native file name, attribute) o
On Friday 09 March 2007 05:00, Ron Blaschke wrote:
> Attached patch replaces the backslashes with slashes on Windows.
Would using File::Spec be less fragile?
-- c
# New Ticket Created by "Julian Fondren"
# Please include the string: [perl #41764]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=41764 >
Exception severity isn't documented at all, currently, but this
will at least help w
# New Ticket Created by Eric Hanchrow
# Please include the string: [perl #41763]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=41763 >
I noticed that if you cloned an iterator that you had already
"shifted", the clone star
# New Ticket Created by Klaas-Jan Stol
# Please include the string: [perl #41762]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=41762 >
hi,
attached a patch implementing basic function calling for pynie.
* function calli
# New Ticket Created by Jerry Gay
# Please include the string: [perl #41765]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=41765 >
we should have a test which makes sure that all pir/pasm embedded in
pod files parses as va
Thanks! I couldn't get patch to apply the patch, so I applied it by hand.
Committed in r17411.
Hi,
On Fri Mar 09 04:54:12 2007, [EMAIL PROTECTED] wrote:
> attached a patch fixing for languages/pynie:
>
> * // operator (fdiv)
> * prefix:+ operator
> * << and >> operators
>
> tests will follow later.
>
> regards,
> kjs
Looks ok to me, i'll add some tests later for this too.
Thanks, appli
Hi,
On Fri Mar 09 04:54:12 2007, [EMAIL PROTECTED] wrote:
> attached a patch fixing for languages/pynie:
>
> * // operator (fdiv)
> * prefix:+ operator
> * << and >> operators
>
> tests will follow later.
>
> regards,
> kjs
Looks ok to me, i'll add some tests later for this too.
Thanks, appli
On Mon Mar 05 16:57:47 2007, [EMAIL PROTECTED] wrote:
> Two months ago, I filed this bug report (excerpt):
I'm still not seeing the effects of the bug you describe, btw. (on OS X
intel or ppc). It does remind me of issues I had when attempting to use
the GMP libs, though.
> > ...I inferred that s
On 09/03/07, Ron Blaschke <[EMAIL PROTECTED]> wrote:
Will Coleda wrote:
> I expect the first two to pass, but metadata is often often overlooked
> on commits.
>
> The last one is a new test, not everything has been updated yet. (And
> I'm not sure it *can* be without breaking windows).
>
> Should
# New Ticket Created by Klaas-Jan Stol
# Please include the string: [perl #41760]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=41760 >
attached a patch fixing for languages/pynie:
* // operator (fdiv)
* prefix:+ operator
Will Coleda wrote:
I expect the first two to pass, but metadata is often often overlooked
on commits.
The last one is a new test, not everything has been updated yet. (And
I'm not sure it *can* be without breaking windows).
Should be passing the second test again as of r17398.
Thanks for y
Hi all,
On Thu Mar 08 15:23:52 2007, [EMAIL PROTECTED] wrote:
> hi,
> attached a patch for pynie:
>
> * fixed rule for floatingpoints and imag.numbers. TGE not correct yet (+
> some reorderings of rules)
> * added compound_stmt TGE
> * added tests to literals, but some are still commented out (n
James E Keenan wrote:
Klaas-Jan Stol wrote:
hi,
I've started a bit on a PIR tutorial on the wiki.
If anybody can spare a few moments, some feedback would be very welcome!
I am very glad to see this. One suggestion and one request for
clarification:
1. First bullet point in FAQ should be:
hi,
In PIR, it's allowed to use ops as names for variables. For instance,
it's allowed to write:
.sub main
.local pmc inc
.end
However, when trying to increment your variable 'inc', you could write
.sub main
.local pmc inc
inc inc
.end
which not only looks strange, but will not even comp
hi,
on
http://www.parrotcode.org/resources.html
there's a link named "glossary".
clicking on that link results in an empty page. The glossary is in
docs/glossary.pod
It should be put it in the website repository too.
regards,
kjs
22 matches
Mail list logo
