# New Ticket Created by Nick Kostirya
# Please include the string: [perl #24376]
# in the subject line of all future correspondence about this issue.
# URL: http://rt.perl.org/rt2/Ticket/Display.html?id=24376
Hello.
With this patch Parrot is being successfully built on NetBSD 1.6.
Nick.
# New Ticket Created by David Robins
# Please include the string: [perl #24378]
# in the subject line of all future correspondence about this issue.
# URL: http://rt.perl.org/rt2/Ticket/Display.html?id=24378
In a clean build from latest CVS sources, I get:
src/cpu_dep.c
src/cpu_dep.c, line
On Thu, 30 Oct 2003, Melvin Smith wrote:
At 12:09 AM 10/31/2003 +, Nicholas Clark wrote:
On Thu, Oct 30, 2003 at 01:54:24AM -0500, Melvin Smith wrote:
Parrot fetched its first web page tonight. Its a baby step, but hey... :)
Can we do IPv6?
snip
Some of the changes are pretty simple
At 09:16 AM 10/31/2003 -0500, David Robins wrote:
On Thu, 30 Oct 2003, Melvin Smith wrote:
At 12:09 AM 10/31/2003 +, Nicholas Clark wrote:
On Thu, Oct 30, 2003 at 01:54:24AM -0500, Melvin Smith wrote:
Parrot fetched its first web page tonight. Its a baby step, but
hey... :)
Can we do
While not totally through it, I'm currently making good progress in
following release instruction's 10a). Thanks to Steve to put that file
together, it went all smoothly.
I hope that all announces got it to their recipients and that everything
is working fine.
Have fun,
leo, going tonight zum
# New Ticket Created by Simon Glover
# Please include the string: [perl #24381]
# in the subject line of all future correspondence about this issue.
# URL: http://rt.perl.org/rt2/Ticket/Display.html?id=24381
An attempt to build Parrot with PIO_OS_STDIO defined (as is the case
when you're
I resolved #24030 and #24038 by changing the Status field and hitting
Save Changes, then I noticed there was a Resolve option on the top
righthand side which asks for details for a notification email. I'm
wondering which is the approved way?
Either is fine. By default the Resolve page
At 07:34 PM 10/31/2003 -0500, Josh Wilmes wrote:
Very cute!
However, i'm curious about the choice of interface. Having individual
ops for something like a socket API seems rather peculiar to me.
Why do we not have an object oriented interface on a socket class?
(ditto for non-trivial file IO)
# New Ticket Created by Adam Thomason
# Please include the string: [perl #24371]
# in the subject line of all future correspondence about this issue.
# URL: http://rt.perl.org/rt2/Ticket/Display.html?id=24371
A few tests using output_like and friends have unescaped '.' chars. These aren't
Reeducation succeeded.
I resolved #24030 and #24038 by changing the Status field and hitting
Save Changes, then I noticed there was a Resolve option on the top
righthand side which asks for details for a notification email. I'm
wondering which is the approved way?
I ask because I'll add a
Anything that uses the Ceach operator is a prime candidate for
bugginess. Please keep an eye out for them as you do your testing.
Any function that contains Ceach oughta be heavily checked.
Ditto anything that uses Ckeys or Cvalues without a sort.
xoa
--
Andy Lester
[EMAIL PROTECTED],
I just put out Test-Harness-2.31_02.tar.gz. Please download and start
beating on it. I'm especially interested in people using the new
Fprove utility. It's for testing .t files without having to run make
test, as in:
prove t/*.t
or just
prove t/
or
prove -v -b -r t/ # -v
I've added functionality to strip POD entirely and to stub blank
lines. I've
also gutted the implementation trying to save characters (literally,
individual
characters) wherever possible. I've got it down to 342 kB. There isn't
much more
room to squeeze stuff out.
Personally, I find the POD
Parrot 0.0.13 Screaming Pumpkin Released!
Your new Bluza[1] proudly presents Parrot 0.0.13 Halloween edition[2].
Proposed originally as a fun release it has a remarkable list of
improvements, additions, and fixes[3].
While not really milestones are reached, many steps towards these are
14 matches
Mail list logo
