On Monday 24 December 2007 19:40:46 James Keenan via RT wrote:
> Is this solution too naïve?
>
> $> perl -Ilib/ -MFile::Which -le '$location=which('fink');print "loc:
> $location";'
> loc: /sw/bin/fink
>
> We have File::Which available to us in the Parrot distribution. Is
> there some reason why
Is this solution too naïve?
$> perl -Ilib/ -MFile::Which -le '$location=which('fink');print "loc:
$location";'
loc: /sw/bin/fink
We have File::Which available to us in the Parrot distribution. Is
there some reason why it could *not* be used here?
kid51
The test coverage is about as high as I can push it, so I'm resolving
this ticket.
From: "James Keenan via RT" <[EMAIL PROTECTED]>
Date: Mon, 24 Dec 2007 19:14:45 -0800
Thanks, Bob. Do you know if there's any definitive source on the
history of perldoc in relation to Perl versions?
Not that I'm aware of. I just poked around in the two oldest Perl
installations I h
On Mon Dec 24 18:50:18 2007, rgrjr wrote:
>
>
> FWIW, the perldoc that shipped with 5.8.0 is version 2.03, and it
> doesn't handle the "-d" option, which was added in 5.8.1.
>
> -- Bob Rogers
> http://rgrjr.dyndns.
In r24198, some of the content of runstep() was refactored into 4
internal subroutines, which were then tested in 2 new test files.
High test coverage was achieved by refactoring some of the guts of
runstep() into 3 internal subroutines/methods, and then writing
additional test files to exercise that code. Committed to trunk in r24197.
From: "James Keenan via RT" <[EMAIL PROTECTED]>
Date: Mon, 24 Dec 2007 17:46:47 -0800
On Thu Nov 01 18:53:47 2007, [EMAIL PROTECTED] wrote:
> (BTW, does anyone know when the different versions of 'perldoc' were
> introduced? Googling for 'perldoc version 1' was unproductive, and I
From: "James Keenan via RT" <[EMAIL PROTECTED]>
Date: Mon, 24 Dec 2007 17:46:47 -0800
On Thu Nov 01 18:53:47 2007, [EMAIL PROTECTED] wrote:
> (BTW, does anyone know when the different versions of 'perldoc' were
> introduced? Googling for 'perldoc version 1' was unproductive, and I
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('perldoc -ud c99da7c4.tmp perldoc') ||
> undef;
>
> if
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 with src/gc/res_lea.c. This
doesn't work. See [perl #42774].
auto::funcptr: In r24193, I refactored code out of runstep() into
_cast_void_pointers_msg() and _set_positive_result(). I renamed one
test file, gave it new content and added two more test files.
The remaining uncovered code deals with the case where there are
problems identifying the user's JIT
James Keenan via RT wrote:
I haven't completely sorted through the above issues, but here's a
somewhat refactored module and two test files. Because of issues
discussed in RT 48070, I'm suggesting the use of IO::CaptureOutput
rather than Parrot::IO::Capture::Mini for capturing verbose output.
I
The patch proposes to split Parrot configuration step auto::jit into two
steps, auto::arch and auto::jit.
The rationale for this patch is that currently config/auto/jit.pm has,
in its runstep() method, two distinct tasks: determining the CPU
architecture and the operating system on the one hand;
On Dec 24, 3:01 am, [EMAIL PROTECTED] (Stephen Weeks)
wrote:
> # New Ticket Created by Stephen Weeks
> # Please include the string: [perl #49061]
> # in the subject line of all future correspondence about this issue.
> # http://rt.perl.org/rt3/Ticket/Display.html?id=49061>
>
> Working on getting
Parrot Bug Summary
http://rt.perl.org/rt3/NoAuth/parrot/Overview.html
Generated at Mon Dec 24 14:00:04 2007 GMT
---
* Numbers
* New Issues
* Overview of Open Issues
* Ticket Status By Version
* Requestors with m
In r24183, code was refactored out of runstep() into _set_intvalfmt() and
_set_floatvalfmt_nvsize(). Rename 130-auto_format.t to
130-auto_format-01.t and add 130-auto_format-02.t. Code coverage is
100% for statement, branch, condition, subroutine, so ticket can be closed.
17 matches
Mail list logo
