i removed a stray line of imcc code which accidentally converted an
op's full name back to it's short name (e.g. branch_p => branch). this
should make errors for missing ops or bad arguments easier to
understand, as the op full name, short name, and arg count is now
reported in the error message.
forgot to copy p6i
> [particle - Fri Nov 11 11:41:28 2005]:
>
> > [leo - Tue May 10 05:13:47 2005]:
> [above code snipped]
> > As a starter an equivalent of File::Spec::catfile() would suffice to be
> > able to rewrite above code.
> >
> File::Spec::catdir() has been implemented for win32. catfi
has this been addressed, even partially? it seems that it has, but this
ticket, nor the related email thread
(http://www.nntp.perl.org/group/perl.perl6.internals/29394) has been
updated since may 2005.
~jerry
On Fri, Nov 11, 2005 at 02:26:13PM -0800, jerry gay wrote:
> On 11/11/05, Joshua Hoblitt <[EMAIL PROTECTED]> wrote:
> > I think it makes sense to rename the files to be .pm anyways as they're
> > already more of a module then a script and will only become more so.
> >
> please rename them, as we di
On Fri, Nov 11, 2005 at 05:17:30PM -0500, Will Coleda wrote:
>
> On Nov 11, 2005, at 5:15 PM, Joshua Hoblitt wrote:
> >
> >As in my original proposal, Configure.pl would have to set the order
> >that the steps run in. Longer term it'd be nice to build a dependency
> >tree between the steps and ex
On 11/11/05, Joshua Hoblitt <[EMAIL PROTECTED]> wrote:
> I think it makes sense to rename the files to be .pm anyways as they're
> already more of a module then a script and will only become more so.
>
please rename them, as we discussed on #parrot. they can't be run as
standalone scripts, so the .
On Nov 11, 2005, at 5:15 PM, Joshua Hoblitt wrote:
On Thu, Nov 10, 2005 at 11:51:44AM +0100, Leopold Toetsch wrote:
Joshua Hoblitt wrote:
I've taken a look at using Module::Pluggable to register configure
steps. The simplest way to do this is to let Module::Pluggable
search
through the ./c
On Thu, Nov 10, 2005 at 11:51:44AM +0100, Leopold Toetsch wrote:
> Joshua Hoblitt wrote:
> >I've taken a look at using Module::Pluggable to register configure
> >steps. The simplest way to do this is to let Module::Pluggable search
> >through the ./config directory. This requires renaming all of
On Thu, Nov 10, 2005 at 10:16:14AM +, Simon Wistow wrote:
> On Wed, Nov 09, 2005 at 05:57:22PM -1000, Joshua Hoblitt said:
> > I've taken a look at using Module::Pluggable to register configure
> > steps. The simplest way to do this is to let Module::Pluggable search
> > through the ./config d
Leo has been kind enough to implement this, any many other unicode functions,
enabling Tcl to
once again pass 100% of its tests (with just a little cheating).
leo++
--
matt diephouse
On Thu, 2005-11-10 at 20:51 -0800, Jerry Gay via RT wrote:
> i have a sneaking suspicion that this test no longer fails, but there
> are no smoke reports for ppc-linux for me to verify. is there someone
> with that cpu/arch combo who can produce a test result to either prove
> or disprove my claim
I wrote:
> > Is it documented anywhere what are the legal names for a PMC?
Leo replied:
> To me it seems that the created C code is the limiting thing here
> ... a PMC name has to follow rules of a C identifier.
That makes sense. Also, it seems that two PMC names should not differ
only by letter
Roger Browne wrote:
Is it documented anywhere what are the legal names for a PMC?
I tried to use the name "AMBER::BOOLEAN" but pmc2c objects with:
bad block open: ::BOOLEAN ...
at /home/install/parrot/svn/build_tools/pmc2c.pl line 355,
To me it seems that the created C code is the limit
Is it documented anywhere what are the legal names for a PMC?
I tried to use the name "AMBER::BOOLEAN" but pmc2c objects with:
bad block open: ::BOOLEAN ...
at /home/install/parrot/svn/build_tools/pmc2c.pl line 355,
<$fh> line 1.
It works if I follow the Python/TCL/Perl pattern and use
i have a sneaking suspicion that this test no longer fails, but there
are no smoke reports for ppc-linux for me to verify. is there someone
with that cpu/arch combo who can produce a test result to either prove
or disprove my claim?
~jerry
# New Ticket Created by Allison Randal
# Please include the string: [perl #37655]
# in the subject line of all future correspondence about this issue.
# https://rt.perl.org/rt3/Ticket/Display.html?id=37655 >
On my box, this warning pops up in the middle of t/perl/manifest at 2/5:
Use of unin
16 matches
Mail list logo
