# New Ticket Created by "Paul Cochrane"
# Please include the string: [perl #40589]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=40589 >
Hi,
This patch adds the C, C and C
tests to the default list of tests run when one p
# New Ticket Created by "Paul Cochrane"
# Please include the string: [perl #40590]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=40590 >
Hi,
This patch reduces the amount of output generated by the
t/codingstd/tabs.t test
From: François PERRAD <[EMAIL PROTECTED]>
Date: Mon, 23 Oct 2006 18:51:03 +0200
In languages/lua/lib/thread.pir, I create a Lua thread type by extension of
Parrot::Coroutine.
So I add a lot of methods for Lua type, but I think that 2 of these methods
could be integrated in Par
# New Ticket Created by "Paul Cochrane"
# Please include the string: [perl #40592]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=40592 >
Hi,
This patch: replaces the pattern match operators used so that vim can
syntax hig
# New Ticket Created by Jerry Gay
# Please include the string: [perl #40593]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=40593 >
this test differs from other coding standard test in output format:
~ should display filena
Not all tests follow the "one test reporting on many files" paradigm:
see t/codingstd/perlcritic.t
FWIW,in general, I prefer the perlcritic method.
On Oct 24, 2006, at 5:32 PM, Jerry Gay (via RT) wrote:
# New Ticket Created by Jerry Gay
# Please include the string: [perl #40593]
# in the s
On 10/23/06, Jonathan Worthington <[EMAIL PROTECTED]> wrote:
Karl Forner wrote:
> I've added one C src file, say src/foo.c, and include/parrot/foo.h, and
a
> test in t/src/foo.t.
> I've changed the MANIFEST file accordingly, but I can not manage to
> have my
> foo.o file to be added in libparrot
Amos and Chris,
Thanks for the feedback! I've updated the patch to use C
instead of C, and it is attached to this email.
Further to my question:
so do C and C get
evaluated at different times? I'm trying to understand why one
generates a compile-time error, whereas the other generates the
exp
From: "Paul Cochrane" <[EMAIL PROTECTED]>
Date: Tue, 24 Oct 2006 11:49:23 +0200
Amos and Chris,
Thanks for the feedback! I've updated the patch to use C
instead of C, and it is attached to this email.
Further to my question:
so do C and C get
evaluated at different time
chromatic wrote:
On Monday 23 October 2006 09:49, Jonathan Worthington wrote:
Would it be a good idea to start collecting requirements together from
different language implementors so that when the time comes to work on
the OO PDD, there is already a good description of what it needs to do?
P
To wrap up (or restart) the thread, here are some thoughts from a
high-level view:
HLL classnames should live in the symbol table (i.e. namespace), not in
Parrot's internal class registry. Yes, this means PIR/POST will need
different syntax for instantiating objects from HLL classes. But the
11 matches
Mail list logo
