Andy,
> Then create a new lint target to support Sun Studio.
You've done this recently, haven't you?
> And update the tags target.
What does ctags point to on your system(s)? On mine it's the emacs
version of ctags, whereas the tags target in the makefile is for
exuberant-ctags, which on my
# New Ticket Created by Will Coleda
# Please include the string: [perl #43613]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=43613 >
This op has been long deprecated. it should be removed.
--
Will "Coke" Coleda
[EMAIL PR
Hi Conrad,
Thanks for following up with this. (I believe we talked about this once
before, quite a while ago.)
I'll be able to follow up with you about this later this weekend. (I'm on
vacation right now, waiting for a flight to get me into Toronto later this
afternoon. Then, laundry, and fina
As I suspected, this was not a Parrot problem. diakopter provided the
diagnosis on IRC: In April, Debian re-classified Sarge (3.1) as
"oldstable" and Etch (4.0) as stable. My /etc/apt/sources.list simply
pointed to "stable" to get packages. So when I requested the flex
upgrade, it got that pack
Failed for me to day on Debian 4.0 Linux:
[li11-226:parrot] 510 $ prove -v t/examples/shootout.t
t/examples/shootout1..20
ok 1 - examples/shootout/ack.pir
ok 2 - examples/shootout/binarytrees.pir
ok 3 - examples/shootout/fannkuch.pir
ok 4 - examples/shootout/fasta.pir
ok 5 - examples/shootou
I'm tracking down potential memory corruption with my sentinel patch. Here's
something really weird:
$ prove t/op/trans.t
t/op/transNOK 19/22
# Failed test (t/op/trans.t at line 511)
# Exited with error code: 134
# Received:
# Aborte
# New Ticket Created by Bob Wilkinson
# Please include the string: [perl #43623]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=43623 >
Hello
I can imagine that a tiger does bite tightly, but ...
[EMAIL PROTECTED]:~/
Many thanks! Applied as r19683.
