From: Joshua Juran <[EMAIL PROTECTED]>
Date: Sat, 25 Jun 2005 01:05:35 -0400
On Jun 24, 2005, at 11:02 PM, Bob Rogers wrote:
> Since Complex could also be considered a Number, but of a very
> different
> sort, it might be worth constructing the type hierarchy to reflect
> t
# New Ticket Created by Craig
# Please include the string: [perl #36385]
# in the subject line of all future correspondence about this issue.
# https://rt.perl.org/rt3/Ticket/Display.html?id=36385 >
Downloaded revision 8443 of Parrot to Windows XP Pro using SVN. When using
'nmake' 7.10.3077,
Hi,
What is parrot's default method resolution order? Is it like the old
Python MRO (left-to-right, depth-first)? Is it like the new Python MRO
[1] (left-to-right, depth-first, but discard all but the last occurrence
of duplicates)?
[1] "Unifying types and classes in Python 2.2" by Guido van Ross
I've just checked in changes to PGE that enable it to support
grammars, as well as some more built-in rules (,
, , , etc.). To create a new grammar,
just create a subclass of "PGE::Rule" and install new rules into
the new grammar's namespace:
.sub main @MAIN
load_bytecode "PGE.pbc"
Currently, throwing is_deeply() a code ref causes it to barf.
perl -MTest::More -wle 'print is_deeply sub {}, sub {}'
WHOA! No type in _deep_check
This should never happen! Please contact the author immediately!
# Looks like your test died before it could output anything.
is_deeply() doesn't k
I'll chime in, as I'm the one who initially raised the idea : )
I'll start with a use-case: my initial motivation for having is_deeply
handle coderefs came up while building certain unit tests for a
rewrite of DBD::Mock. Several of the worker functions return complex
data structures -- which may c
On Sun, Jun 26, 2005 at 12:08:35AM -0400, Collin Winter wrote:
> My inital strategy for implementing this was a two-tiered approach.
> First, compare the references; if they're the same, return true, go no
> futher. If they differ, however, say if anonymous subs were thrown
> into the mix, then use
> > My initial quick-glance at B::Deparse's documentation mentions
> > something about perl optimising certain constants away, which could
> > well throw a spanner into the works. Storable uses B::Deparse when
> > serialising coderefs, though, so I'm certain there's a way around
> > this.
>
> That
I've just uploaded Test::Harness 2.51_02. It turns off the timer by
default, and adds a --timer switch to prove. Please try it out and see
if all is well because I'm going to make it 2.52 tomorrow.
And now, I must go to bed so I can drive to Toronto...
xoxo,
Andy
--
Andy Lester => [EMAIL PROT
