Re: [perl #44353] [BUG] Configure.pl: verbose-step option not working with named step

Joshua Hoblitt wrote: The issue is here is that there is nothing in Configure.pl's output to correlate the package name of the step with the output seen from a typical run. For example, say the test that outputs "Determining architecture, OS and JIT capability..." is failing

[perl #44363] [PATCH] -D80 + bad luck = segfault

# New Ticket Created by Bram Geron # Please include the string: [perl #44363] # in the subject line of all future correspondence about this issue. # http://rt.perl.org/rt3/Ticket/Display.html?id=44363 > At Parrot exit, we force-destroy all PObjs. It can happen that a context is destroyed afte

[svn ci] increased warnings levels for msvc

if you windows developers suddenly notice that your build output is full of warnings, it's because we've increased the warnings level from -W3 to -W4. since some level four warnings are so noisy, we've disabled a few of them, until we get the others under control. if you have msvc and an eye for f

Re: [svn:parrot] r20446 - trunk/config/auto

On Aug 3, 2007, at 8:19 AM, [EMAIL PROTECTED] wrote: Modified: trunk/config/auto/gcc.pm Log: [config] Started doing some cleaning of the warnings setting code for gcc I'm going to be gutting all this gcc code in a day or two anyway, making it autosniff capabilities like the autosniff

[perl #44351] [PATCH] GC_VERBOSE=1 + tracing = segfault

# New Ticket Created by Bram Geron # Please include the string: [perl #44351] # in the subject line of all future correspondence about this issue. # http://rt.perl.org/rt3/Ticket/Display.html?id=44351 > When GC_VERBOSE=1 and tracing is on, Parrot spits out messages about PObjs getting destroy

Re: [perl #44345] [PATCH] Add NQP to docs/glossary.pod

>The attached patch adds NQP to the glossary in the docs directory. > The attached, corrected patch gives the correct definition for NQP. Colin Index: docs/glossary.pod === --- docs/glossary.pod

[perl #44213] docs/faq.pod - fix L pod abuse

Seems like a pretty straightforward patch, but isn't the L<> syntax used currently proper? Is there a particular pod reader we're trying to make happy?

[perl #44393] something funny in dod/gc blocking macros

# New Ticket Created by Jerry Gay # Please include the string: [perl #44393] # in the subject line of all future correspondence about this issue. # http://rt.perl.org/rt3/Ticket/Display.html?id=44393 > i'm having trouble on x86_64. when running a 32bit parrot, i get occasional deadlock at the

[perl #44393] something funny in dod/gc blocking macros

hi, i'm a blockhead. ron reminded me that i'm not following C89, since node was not defined at the top of a block. duh. anyway, this doesn't seem to fix the problem. rats. i must misunderstand the comment, because i find it hard to believe that adding these few lines of code is enough to address a

Re: [perl #44393] something funny in dod/gc blocking macros

On Friday 03 August 2007 13:29:53 Jerry Gay wrote: > i'm having trouble on x86_64. when running a 32bit parrot, i get > occasional deadlock at the OS level, after Parrot_exit. when running a > 64bit parrot, it segfaults within Parrot_exit, while running the exit > handlers. if i run with -G, no se

Re: [perl #44213] docs/faq.pod - fix L pod abuse

Will Coleda via RT wrote: > Seems like a pretty straightforward patch, but isn't the L<> syntax > used currently proper? Is there a particular pod reader we're trying > to make happy? I tripped over this recently too. >From perlpod: * "L" Links to an absolute URL. For example, "L

Re: [perl #44213] docs/faq.pod - fix L pod abuse

# from Will Coleda via RT # on Friday 03 August 2007 01:40 pm: >Seems like a pretty straightforward patch, but isn't the L<> syntax >used currently proper? The L<> doesn't support "named" http:// links. from perlpod: ' L Links to an absolute URL. For example, L. But not

Re: [perl #44379] config/auto/attributes.pm ought to use its own test_c.in

On 8/3/07, via RT Andy Dougherty <[EMAIL PROTECTED]> wrote: > # New Ticket Created by Andy Dougherty > # Please include the string: [perl #44379] > # in the subject line of all future correspondence about this issue. > # http://rt.perl.org/rt3/Ticket/Display.html?id=44379 > > > > The new attribut

[perl #44379] config/auto/attributes.pm ought to use its own test_c.in

# New Ticket Created by Andy Dougherty # Please include the string: [perl #44379] # in the subject line of all future correspondence about this issue. # http://rt.perl.org/rt3/Ticket/Display.html?id=44379 > The new attributes scanning ought to use its own test_c.in file, instead of trying to

[perl #44381] Should Configure.pl scan for __attribute__ at all?

# New Ticket Created by Andy Dougherty # Please include the string: [perl #44381] # in the subject line of all future correspondence about this issue. # http://rt.perl.org/rt3/Ticket/Display.html?id=44381 > Thinking *way* ahead, I wonder if Configure.pl should even bother scanning for __attr

[perl #44395] Lexical scopes are too coarse-grained for loops.

# New Ticket Created by Bob Rogers # Please include the string: [perl #44395] # in the subject line of all future correspondence about this issue. # http://rt.perl.org/rt3/Ticket/Display.html?id=44395 > The problem arises when blocks with closed-over lexical bindings are executed more tha

[perl #44391] r19820 breaks other JITs

# New Ticket Created by Joshua Isom # Please include the string: [perl #44391] # in the subject line of all future correspondence about this issue. # http://rt.perl.org/rt3/Ticket/Display.html?id=44391 > After a fair amount of headaches, I finally discovered some of my trouble with my jit.

[svn:perl6-synopsis] r14432 - doc/trunk/design/syn

Author: larry Date: Fri Aug 3 18:27:52 2007 New Revision: 14432 Modified: doc/trunk/design/syn/S05.pod doc/trunk/design/syn/S06.pod Log: Clarification of meaning of form as non-interpolating Restriction of placeholder names to lowercase to help us catch $^O et al. Modified: doc/trunk/de

[svn:perl6-synopsis] r14433 - doc/trunk/design/syn

Author: larry Date: Fri Aug 3 18:40:13 2007 New Revision: 14433 Modified: doc/trunk/design/syn/S05.pod Log: date typo Modified: doc/trunk/design/syn/S05.pod == --- doc/trunk/design/syn/S05.pod(original) +++

[perl #44389] Excessive warnings on Apple's gcc 3.3 wrt attributes

# New Ticket Created by Joshua Isom # Please include the string: [perl #44389] # in the subject line of all future correspondence about this issue. # http://rt.perl.org/rt3/Ticket/Display.html?id=44389 > The new attribute configure code seems to get a false positive with warn_unused_result o

Re: [perl #44389] Excessive warnings on Apple's gcc 3.3 wrt attributes

Joshua Isom wrote: # New Ticket Created by Joshua Isom # Please include the string: [perl #44389] # in the subject line of all future correspondence about this issue. # http://rt.perl.org/rt3/Ticket/Display.html?id=44389 > The new attribute configure code seems to get a false positive with

Re: [perl #44395] Lexical scopes are too coarse-grained for loops.

On Fri, Aug 03, 2007 at 03:37:39PM -0700, Bob Rogers wrote: >A naive PIR implementation of this loop is included as the second > attachment. It fails miserably, because PIR can't distinguish between > the different scopes for "$i" and "$n". > > sub make_closures_loop { > # Return n closur

Re: [perl #44395] Lexical scopes are too coarse-grained for loops

Perhaps ignore my earlier message -- this one is more coherent. On Fri, Aug 03, 2007 at 03:37:39PM -0700, Bob Rogers wrote: > sub make_closures_loop { > # Return $n closures, each with lexical references to $i and $n. > my $n = shift; > > my @result; >

Re: [perl #44395] Lexical scopes are too coarse-grained for loops

On Fri, Aug 03, 2007 at 09:51:53PM -0500, Patrick R. Michaud wrote: > >Currently, the only way to get a distinct binding for each "$i" in > > PIR is to factor the loop body out into a separate lexical sub. This is > > far from ideal, not least because it is not transparent to the HLL user. >

Re: [perl #44395] Lexical scopes are too coarse-grained for loops

From: "Patrick R. Michaud" <[EMAIL PROTECTED]> Date: Fri, 3 Aug 2007 21:51:53 -0500 Perhaps ignore my earlier message -- this one is more coherent. I haven't gotten that one yet. (Must have been via RT. Now if I could only remember to send all my incoherent posts via RT. ;-) On Fr

Re: [perl #37287] [TODO] pdb - don't die on exceptions

> This patch makes parrot stop execution of the vm when running as a > debugger. > > This makes the pdb stop executing and shows the exception message > instead of silently exiting. Hi, pancake! I have tried to update your patch to svn r20469, see attached patch. Unfortunately, it doesn't work a

Re: [perl #44389] Excessive warnings on Apple's gcc 3.3 wrt attributes

On Friday 03 August 2007 18:45:37 James E Keenan wrote: > Confirmed.  Over the last few weeks, my log of my 'make' output on > Darwin has tended to run in the range of 70-73K.  Tonight it ran to > over 7.1M. r20454 doesn't help. Of course, it looks like that's papering over the fact that the no

[svn:parrot-pdd] r20471 - trunk/docs/pdds

Author: allison Date: Fri Aug 3 23:48:13 2007 New Revision: 20471 Modified: trunk/docs/pdds/pdd15_objects.pod Log: [pdd] Add a vtable function for adding vtable overrides to classes and roles. Modified: trunk/docs/pdds/pdd15_objects.pod ==