On Jun 29, 2007, at 12:28 PM, Bernhard Schmalhofer via RT wrote:
James Keenan via RT schrieb:
There was code in several of the test files in the reconfigure/
branch which was repeated. At
the hackathon, David Adler refactored it into a subroutine which I
then placed in new file
Auxiliary.p
James Keenan via RT schrieb:
There was code in several of the test files in the reconfigure/ branch which was repeated. At
the hackathon, David Adler refactored it into a subroutine which I then placed in new file
Auxiliary.pm. That file is contained in this patch along with a revised t/104-in
There was code in several of the test files in the reconfigure/ branch which
was repeated. At
the hackathon, David Adler refactored it into a subroutine which I then placed
in new file
Auxiliary.pm. That file is contained in this patch along with a revised
t/104-init_miniparrot.t
and approp
Applied to trunk in r19420.
On Tue Jun 26 07:50:06 2007, jkeen at verizon.net wrote:
>
> But it's not clear how one can validate that the result will "match
> ANSI characteristics." Is
> there any link we could place in the POD that would show which ANSI C
> characteristics we
> need to have miniparrot match?
>
I've got
The POD for config/init/miniparrot.pm states:
Modifies settings to match miniparrot (ANSI C Parrot)'s needs. This step
primarily overwrites a lot of settings in the Configure database to disable
JIT and *match ANSI characteristics* (emphasis added).
How this package disables JIT is fairly self-e
# New Ticket Created by James Keenan
# Please include the string: [perl #43342]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=43342 >
Write unit tests for config/init/miniparrot.pm,
the module whose functionality executes
