Re: [perl #46513] [BUG] t/pmc/exporter.t test failures

2007-10-18 Thread James E Keenan
chromatic wrote: On Wednesday 17 October 2007 19:30:09 James Keenan wrote: --- t/pmc/exporter.t2 512122 2-3 Failed 1/1 test scripts. 2/12 subtests failed. Files=1, Tests=12, 1 wallclock secs ( 0.27 cu

[perl #46513] [BUG] t/pmc/exporter.t test failures

2007-10-18 Thread James Keenan via RT
Verified on Linux and Darwin that whatever chromatic did fixed this bug. (The others I reported are still outstanding on both OSes.) kid51

Re: [perl #43661] [CAGE] Get parrot configuration to autodiscover gcc warning flags

2007-10-18 Thread Paul Cochrane
On 15/10/2007, James E Keenan <[EMAIL PROTECTED]> wrote: > Paul Cochrane via RT wrote: > > On Sun Jul 08 15:09:19 2007, ptc wrote: > >> At present we have to specify warnings flags for each version of gcc > >> (see config/auto/gcc.pm). This is a pain. Perl 5 is able to work out > >> automatically

Re: [perl #43661] [CAGE] Get parrot configuration to autodiscover gcc warning flags

2007-10-18 Thread Paul Cochrane
> 4. Can you answer the question I posed in my July 8 response to your > original post? I can't find anything relevant on July the 8th, although there was an email on Sep the 8th... Is there a ticket number or another pointer you can give me? Thanks! Paul

Re: [svn:parrot] r22206 - trunk/t/codingstd

2007-10-18 Thread chromatic
On Thursday 18 October 2007 08:57:51 [EMAIL PROTECTED] wrote: > +ok( !scalar(@multi_dots), 'No multi-dot filenames' ) > +    or diag( "Multi-dot filename found in " . scalar @multi_dots > +        . " files:[EMAIL PROTECTED]" ); Both instances of scalar() are redundant here. The bang operator en

[svn:parrot-pdd] r22234 - trunk/docs/pdds/draft

2007-10-18 Thread paultcochrane
Author: paultcochrane Date: Thu Oct 18 11:58:53 2007 New Revision: 22234 Modified: trunk/docs/pdds/draft/pdd09_gc.pod trunk/docs/pdds/draft/pdd16_native_call.pod Log: [docs/pdds] Basic reformat of some paragraphs. This has the positive side effect of lines not exceeding the 100 character l

Re: [perl #39824] [CAGE] tools/dev/check_source_standards.pl -- this should be a test

2007-10-18 Thread Paul Cochrane
Hi all, there is now a test in t/codingstds called filenames.t which encapsulates the discussion here. Is this sufficient to now close this ticket and to remove the old check_source_standards.pl program? Paul

Re: [perl #39824] [CAGE] tools/dev/check_source_standards.pl -- this should be a test

2007-10-18 Thread jerry gay
On 10/18/07, Paul Cochrane <[EMAIL PROTECTED]> wrote: > there is now a test in t/codingstds called filenames.t which > encapsulates the discussion here. Is this sufficient to now close > this ticket and to remove the old check_source_standards.pl program? > yes, i believe your solution meets the c

Re: [perl #38969] [CAGE] parrot source does not conform to standards

2007-10-18 Thread jerry gay
On 10/18/07, Paul Cochrane via RT <[EMAIL PROTECTED]> wrote: > > http://rt.perl.org/rt3/Ticket/Display.html?id=39824 > > Since the above ticket has now been resolved, does this mean that this > ticket can also be resolved? > yes, i believe we've addressed all the points in this ticket well enough t

Re: [RFE] Allow comment lines in PIR .param list

2007-10-18 Thread Klaas-Jan
On Oct 18, 1:28 am, [EMAIL PROTECTED] (Jerry Gay) wrote: > On 10/17/07, via RT Bernhard Schmalhofer > > <[EMAIL PROTECTED]> wrote: > > # New Ticket Created by Bernhard Schmalhofer > > # Please include the string: [perl #46499] > > # in the subject line of all future correspondence about this issu

[perl #43661] [CAGE] Get parrot configuration to autodiscover gcc warning flags

2007-10-18 Thread Paul Cochrane via RT
James, Thanks for pointing out what you meant. I think I must have been having a bit of a brain-fade moment or something... On Sun Jul 08 18:06:03 2007, [EMAIL PROTECTED] wrote: > Paul Cochrane wrote: >Perl 5 is able to work out > > automatically the warnings flags of gcc and then use those

[perl #38969] [CAGE] parrot source does not conform to standards

2007-10-18 Thread Paul Cochrane via RT
> http://rt.perl.org/rt3/Ticket/Display.html?id=39824 Since the above ticket has now been resolved, does this mean that this ticket can also be resolved? Paul

Generic callback mechanism in NCI

2007-10-18 Thread parrot
I started to write an OpenGL library and was only a couple of dozen lines into the pir when I remembered the documentation about callbacks in docs/pdds/draft/pdd16_native_call.pod . Currently there are only two signatures supported on callbacks: one with user_data and extern_data and the other wit

Re: [perl #46541] [BUG] t/pmc/objects.t test failures

2007-10-18 Thread chromatic
On Thursday 18 October 2007 18:04:15 James Keenan wrote: > Linux. r22261 > > [li11-226:parrot] 559 $ prove -v t/pmc/objects.t > t/pmc/objects1..74 > ok 1 - find_type (base class) > > [snip] > > not ok 57 - equality of subclassed Integer > > # Failed test (t/pmc/objects.t at line 1668) > #

[perl #43481] t/examples/shootout.t (shootout_16.pir) fails on gentoo/x86

2007-10-18 Thread James Keenan via RT
On Thu Oct 18 19:31:48 2007, [EMAIL PROTECTED] wrote: > I'm not sure about the current status of t/examples/shootout.t on Linux, > but it is still failing on Darwin. See attached. It should be noted that apart from shootout.t, the only failures I'm getting on Darwin are from the same tests which

[perl #45523] [TODO] Have Configure.pl inform user of failed configuration steps

2007-10-18 Thread James Keenan via RT
See patch diff.fatal.revised.txt attached to RT 44525 tonight for an implementation of the listing of failed configuration steps.

[perl #46541] [BUG] t/pmc/objects.t test failures

2007-10-18 Thread via RT
# New Ticket Created by James Keenan # Please include the string: [perl #46541] # in the subject line of all future correspondence about this issue. # http://rt.perl.org/rt3/Ticket/Display.html?id=46541 > Linux. r22261 [li11-226:parrot] 559 $ prove -v t/pmc/objects.t t/pmc/objects1..74

[perl #46539] [BUG] compilers/pirc/new/pir.l failing t/codingstd/cppcomments.t

2007-10-18 Thread via RT
# New Ticket Created by James Keenan # Please include the string: [perl #46539] # in the subject line of all future correspondence about this issue. # http://rt.perl.org/rt3/Ticket/Display.html?id=46539 > Looks like code starting at line 298 is being interpreted as a C++- style comment. [

[perl #46517] [BUG] t/stm/llqueue.t test failures

2007-10-18 Thread Allison Randal via RT
Resolved in r22217.

[perl #43481] t/examples/shootout.t (shootout_16.pir) fails on gentoo/x86

2007-10-18 Thread James Keenan via RT
I'm not sure about the current status of t/examples/shootout.t on Linux, but it is still failing on Darwin. See attached. t/examples/shootout.. # Failed test (t/examples/shootout.t at line 108) # Exited with error code: [SIGNAL 10] # Received: # # Expected: # P4 # 200