# New Ticket Created by Colin Kuskie
# Please include the string: [perl #44211]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=44211 >
Please try running either the pi.t or e.t tests from pugs
t/builtins/math/{e,pi}.t.
Wh
# New Ticket Created by Colin Kuskie
# Please include the string: [perl #44209]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=44209 >
The PIR code that defines 'e' was missing a return statement.
The attached patch fixes
Let me preface this by saying that I know that our static analysis tests
represent a tremendous amount of work by several people (especially Paul,
with an enormous amount of respect to everyone who's contributed also to
Perl::Critic and PPI), and that they have helped us reach and do help us
ma
Please close this bug. I needed to do a make clean before
rebuilding.
# New Ticket Created by James Keenan
# Please include the string: [perl #44207]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=44207 >
---
osname= linux
osvers= 2.6.18.3
arch= i486-linux-gnu-thread-multi
cc= cc
---
Fl
# New Ticket Created by Colin Kuskie
# Please include the string: [perl #44205]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=44205 >
When building parrot from scratch, this command gets run:
/usr/bin/perl tools/build/pmc
On Thu, Jul 26, 2007 at 05:51:23PM -0700, Colin Kuskie wrote:
> for (0,1,2) { say $_; }
>
> that construct dies with:
>
> Null PMC access in get_bool()
Now fixed in 20269.
> I checked in an updated 01-sanity/07-for.t into the pugs repository,
> so if t/fetchspec is run you would be setup to
On Thu Jul 26 19:22:57 2007, particle wrote:
> while typing
> perl Configure.pl --nomanicheck ---verbose-step=init::gcc
> --configure_trace
>
> earlier today in order to debug a configure-related problem i was
> having, i felt --configure_trace was too much to type.
>
> i'd like to see --trace
very nice -- i could have used that THIS AFTEROON! :)
On Thu, 26 Jul 2007, Andy Lester wrote:
Josh putting in the new backtrace behind my new assertions makes debugging
assertions SO MUCH EASIER.
I'm gonna go s/assert/PARROT_ASSERT/ everywhere.
xoxo,
Andy
P.S. sample
# Received:
# 1..
