Tonight I again had failures in 3 files in t/tools/ops2pmutils/.
t/tools/ops2pmutils/09-prepare_real_opsok 1/38op get_all_eh_p:
sequence mismatch: ops.num 168 vs. core.ops 1215 at
/home/jimk/work/parrot/lib/Parrot/Ops2pm/Utils.pm line 454.
# Looks like you planned 38 tests but only ran 16.
On Monday 29 October 2007 19:54:11 James Keenan via RT wrote:
> The patch attached provides a refactoring of configuration step class
> auto::byteorder along the same lines as other recent refactorings of
> auto::* config classes, i.e., the code handling the C probe is
> refactored into one intern
The patch attached provides a refactoring of configuration step class
auto::byteorder along the same lines as other recent refactorings of
auto::* config classes, i.e., the code handling the C probe is
refactored into one internal subroutine, while everything that follows
is refactored into an inte
Paul Johnson wrote:
Note that you can merge coverage databases, or generate reports from
more than one database, for this very reason.
If we had people in addition to myself working on these tests, I'd
explore that possibility -- particularly if s/he were on BSD or Win32.
For now, the co
On Mon, Oct 29, 2007 at 04:39:42PM -0700, James Keenan via RT wrote:
> Although the percent of statements in this class's source code covered
> by the test suite and by Configure.pl itself is lower than I normally
> would settle for
> (http://thenceforward.net/parrot/coverage/configure-build/confi
Although the percent of statements in this class's source code covered
by the test suite and by Configure.pl itself is lower than I normally
would settle for
(http://thenceforward.net/parrot/coverage/configure-build/config-auto-va_ptr-pm.html),
the uncovered statements are highly platform-specific.
# New Ticket Created by Bernhard Schmalhofer
# Please include the string: [perl #47011]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=47011 >
In pdd17_pmc.pod it is stated that 'new_from_string' is deprecated.
The existing
Just a few comments from a brief review of pdd19:
> =item 'char constant'
>
> Are delimited by single-quotes (C<'>). They are taken to be ASCII encoded. No
> escape sequences are processed.
What exactly does "They are taken to be ASCII encoded" mean here?
For example, what happens if I write a s
Either config/auto/attributes.pm is now DWIMming or I don't understand
it correctly. Please help me determine which.
Consider the first of two files attached (neither of which is yet in
trunk): t/configure/114-auto_attributes-02.t. It's set up like many of
the other t/configure/*.t tests, no no
Author: allison
Date: Mon Oct 29 10:41:29 2007
New Revision: 22590
Modified:
trunk/docs/pdds/pdd23_exceptions.pod
Log:
[pdd] Add more detail on index value to 'get_eh'.
Modified: trunk/docs/pdds/pdd23_exceptions.pod
>
> Since all the real coding on this package was done before I joined
> the project, I may not be fully aware of its rationale. Was it once
> a configuration step, but then dropped? Is it meant to be an
> optional configuration step?
>
> Would we be better off by reformulating it as a P
Parrot Bug Summary
http://rt.perl.org/rt3/NoAuth/parrot/Overview.html
Generated at Mon Oct 29 13:00:06 2007 GMT
---
* Numbers
* New Issues
* Overview of Open Issues
* Ticket Status By Version
* Requestors with m
At 08:25 27/10/2007 -0700, you wrote:
On Tue Oct 02 13:39:30 2007, [EMAIL PROTECTED] wrote:
> Parrot is no longer licensed under the GPL directly (though it is
> available under the GPL through the Artistic 2.0). Update or remove
> references to the GPL license in these files:
>
> debian/copyrigh
13 matches
Mail list logo
