# New Ticket Created by Jürgen Bömmels
# Please include the string: [perl #23085]
# in the subject line of all future correspondence about this issue.
# URL: http://rt.perl.org/rt2/Ticket/Display.html?id=23085
Hello,
running the testsuite with valgrind (see #23063) produces an error in
J?rgen B?mmels sent the following bits through the ether:
The offending line is exceptions.c:123
if (m[strlen(m-1)] != '\n')
Thanks, applied.
Leon
--
Leon Brocard.http://www.astray.com/
scribot.http://www.scribot.com/
...
On Sun, Jul 20, 2003 at 11:59:00AM -0400, Dan Sugalski wrote:
We're supporting interrupts at the interpreter level because we must.
It doesn't matter much whether we like them, or we think they're a
good idea, the languages we target require them to be there. Perl 5,
Perl 6, Python, and
On Mon, Jul 21, 2003 at 06:29:36PM -0700 it came to pass that Damien Neil wrote:
Do you know of a program that does this (simulated AIO via threads)?
(Again, I'm not disputing your claim--it's just that this is
completely contrary to my experience, and I'd like to know more
about it.)
? cflags.diff
? cflags.tar.gz
? coresplit.diff
? t.tar
Index: config/gen/cflags/imcc.in
===
RCS file: /cvs/public/parrot/config/gen/cflags/imcc.in,v
retrieving revision 1.2
diff -u -a -r1.2 imcc.in
--- config/gen/cflags/imcc.in 22 Jul
On Monday 21 Jul 2003 6:45 pm, Andy Bussey (via RT) wrote:
# New Ticket Created by Andy Bussey
# Please include the string: [perl #23076]
# in the subject line of all future correspondence about this issue.
# URL: http://rt.perl.org/rt2/Ticket/Display.html?id=23076
I assume it should be
I've spent the past day reading through the parrot documentation. I'm a
little confused by pdd06--shouldn't this contain a listing of ALL parrot
opcodes? The first thing I noticed is that print isn't listed there;
shouldn't it be? I'm sure there are lots of other opcodes missing as
well. Is
The TODO list from the current parrot CVS mentions socket IO. Have
opcodes been designated for socket IO yet? Is this up for someone to
start working on?
--TWH
The core.ops split has been committed. Documentation has been fixed up,
and all the copyright stuff should be correct.
Please remember to reassemble any Parrot bytecode files you currently
have.
--Brent Dax [EMAIL PROTECTED]
Perl and Parrot hacker
Yeah, and my underwear is
On Tue, 22 Jul 2003, Brent Dax wrote:
The core.ops split has been committed. Documentation has been fixed up,
and all the copyright stuff should be correct.
Please remember to reassemble any Parrot bytecode files you currently
have.
A fresh checkout builds and tests fine here
Simon Glover:
# A fresh checkout builds and tests fine here (Linux/x86).
I forgot to mention that it tests as well as can be expected on Windows
and Darwin.
# One point - should we update the docs Makefile to spit out
documentation
# for all of the ops files? At the moment we're only doing
On Tue, 22 Jul 2003, Brent Dax wrote:
# One point - should we update the docs Makefile to spit out
documentation
# for all of the ops files? At the moment we're only doing this for
io.ops
# and core.ops (which just got a lot smaller).
This is probably a good idea.
OK, I've just
Tim Howell [EMAIL PROTECTED] writes:
The TODO list from the current parrot CVS mentions socket IO.
Yes.
Have opcodes been designated for socket IO yet?
None that I know of.
The socket IO should be part of the base IO-system. Maybe they should
use another PIO_Layer. This will work at least
Hi,
I've wanted to play with Parrot for some time, and finally found some free
time. So, I downloaded the latest CVS snapshot, extracted it, etc, etc. I
ran Configure.pl, which seemed to go just fine:-
Generating and checking MANIFEST...done.
Setting up Configure's data structures...done.
Jonathan Worthington [EMAIL PROTECTED] writes:
However, the next stage doesn't work out using either perl make.pl or nmake.
=== With nmake ===
C:\Perl\Parrot\parrotnmake
Microsoft (R) Program Maintenance Utility Version 6.00.8168.0
Copyright (C) Microsoft Corp 1988-1998. All rights
Jonathan Worthington:
# cl -nologo -O1 -MD -Zi -DNDEBUG -DWIN32 -D_CONSOLE -DNO_STRICT
-I./include
# -
# DHAS
# _JIT -DI386 -Foparrot.obj -c parrot.c
# parrot.c
# parrot.c(0) : fatal error C1033: cannot open program database
# 'c:\perl\parrot\pa
# rrot\vc60.pdb'
I fixed this earlier today--for
Jonathan Worthington:
# cl -nologo -O1 -MD -Zi -DNDEBUG -DWIN32 -D_CONSOLE -DNO_STRICT
-I./include
# -
# DHAS
# _JIT -DI386 -Foparrot.obj -c parrot.c
# parrot.c
# parrot.c(0) : fatal error C1033: cannot open program database
# 'c:\perl\parrot\pa
# rrot\vc60.pdb'
I fixed this earlier
Yah, I kind of expected that as well the first time I started looking
at the array classes, but if you check:
perldoc docs/pmc/array.pod
and search for out-of-bounds, you'll see it's working as advertised.
If you want an array that grows automatically, PerlArray will do that:
perldoc
Contents are Direct Alliance Corporation CONFIDENTIAL
-
I have a box that could be used. It runs Debian Unstable and really does not
do much. Any interest?
Dual 1.2 G Athlon
512 Megs
Raid 5 36 Gig
This message is for the designated recipient(s) only and contains Direct
Alliance Corporation
Please CC Mr.Sasada on any response.
(I've moved this ticket to the parrot queue.)
-R
=== Forwarded Message:
Date: 22 Jul 2003 08:47:22 -
Subject: [perl #23084] [The Parrot Primer] Japanese Translation
From: K.Sasada via RT
To: AdminCc of perl Ticket #23084: ;
Hi. My name is Koichi
20 matches
Mail list logo
