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

2007-11-30 Thread James Keenan via RT
On Nov 30 2007, ptc wrote: > > https://rt.perl.org/rt3/Ticket/Display.html?id=46539 > > [BUG] compilers/pirc/new/pir.l failing t/codingstd/cppcomments.t > > Coke commented on this on Oct 21, but ticket has not been resolved. > > Spot check of smoke tests suggests it may now be passing on all OSes.

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

2007-10-21 Thread Will Coleda via RT
On Thu Oct 18 18:00:04 2007, [EMAIL PROTECTED] wrote: > Looks like code starting at line 298 is being interpreted as a C++- > style comment. > > > > [li11-226:parrot] 553 $ prove -v t/codingstd/cppcomments.t t > t/codingstd/cppcomments1..1 > > # Failed test (t/codingstd/cppcomments.t a

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

2007-10-20 Thread James Keenan via RT
Still failing as of r22311, Oct 20 2007. t/codingstd/cppcomments..NOK 1/1 # Failed test (t/codingstd/cppcomments.t at line 58) # C++ comments found in 1 files: # /home/jimk/work/parrot/compilers/pirc/new/pir.l: DQ_STRING n])*\>. Does t

[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. [