On Wed Dec 26 14:06:12 2007, doughera wrote:
>
> Or, you could explicitly call the perldoc in $Config{scriptdir}
instead of
> whatever random 'perldoc' happens to occur first in $PATH.
>
Ah, that sounds more like it. I will explore this option.
On Wed, 26 Dec 2007, James Keenan via RT wrote:
> On Wed Dec 26 10:33:28 2007, doughera wrote:
> > On Mon, 24 Dec 2007, James Keenan via RT wrote:
> >
> > > > Given
> > that we
> > > > have decided that Perl 5.8 is the minimum version of Perl you need
> > to
> > > > build Parrot, is there *any* p
On Wed Dec 26 10:33:28 2007, doughera wrote:
> On Mon, 24 Dec 2007, James Keenan via RT wrote:
>
> > > Given
> that we
> > > have decided that Perl 5.8 is the minimum version of Perl you need
> to
> > > build Parrot, is there *any* possibility that someone who gets to
> this
> > > point in configu
On Wednesday 26 December 2007 10:32:46 Andy Dougherty wrote:
> On Mon, 24 Dec 2007, James Keenan via RT wrote:
> > An additional thought: Could someone be using an older version of
> > perldoc if they are using the perldoc provided by an RPM or a .deb?
> Debian certainly supplies 'perldoc' in a
On Wed Dec 26 10:27:33 2007, doughera wrote:
> On Mon, 24 Dec 2007, James Keenan via RT wrote:
>
> >
> > Okay, so if only 1 of the 4 possible values for the --gc option works,
> > why shouldn't we (or, I, as the cage cleaner in this area) just rip out
> > the code for the 3 non-working values?
>
From: Bob Rogers <[EMAIL PROTECTED]>
Date: Mon, 12 Nov 2007 21:32:15 -0500
From: chromatic <[EMAIL PROTECTED]>
Date: Mon, 12 Nov 2007 13:58:51 -0800
. . .
If someone reading this (not just Bob or me) cares to write up some basic
tests and can make a failure c
On Tue, 25 Dec 2007, James Keenan via RT wrote:
> Once I got the tuits, the merging of these two Parrot configuration
> steps went quite quickly. But before applying a patch to trunk, I would
> like the assistance of other testers on the 4 CPU platforms handled by
> gen::cpu and what formerly was
On Mon, 24 Dec 2007, James Keenan via RT wrote:
> On Thu Nov 01 18:53:47 2007, [EMAIL PROTECTED] wrote:
> > In configuration step auto::perldoc there is found this code to probe
> > for the presence of the perldoc utility and, if present, version thereof:
> >
> > my $content = capture_output(
On Mon, 24 Dec 2007, James Keenan via RT wrote:
> Additional question: The POD to this configuration step class states:
>
> "--gc" can take the values:
>
> "gc"
> The default. Use the memory allocator in src/recources.c.
>
> "libc"
> Use the C library "malloc" along
On Dec 25, 2007 4:37 PM, Allison Randal <[EMAIL PROTECTED]> wrote:
> Klaas-Jan Stol wrote:
> > I guess you're right :-) I was thinking of ambiguity, like
> >
> > sub foo :multi(Integer, Integer)
> > .param pmc i :invocant
> > .param pmc j
> > .param pmc k :invocant
> > end
> >
> > sub foo :mult
10 matches
Mail list logo
