Jens Rieks <[EMAIL PROTECTED]> wrote:
> Hmm... no idea what went wrong. I've attached the whole file...
Thanks, applied.
leo
Piers Cawley <[EMAIL PROTECTED]> wrote:
> Leopold Toetsch <[EMAIL PROTECTED]> writes:
>> Piers Cawley <[EMAIL PROTECTED]> wrote:
>>> Leopold Toetsch <[EMAIL PROTECTED]> writes:
>>
The terms are misleading a bit here.
- a ParrotClass isa delegate PMC
- a ParrotObject isa ParrotClass
# New Ticket Created by Stephane Peiry
# Please include the string: [perl #27642]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org:80/rt3/Ticket/Display.html?id=27642 >
This patch fixes a typo in the sun/sparc core.jit where
the first Parrot_sub_n_nc
Dan Sugalski wrote:
So, if I understand this right (and I may well not), when you
instantiate a metaclass you get a class, and when you instantiate a
class you get an object, and since anything you instantiate is an object
anyway that means classes are objects. I'm not entirely sure if
metaclas
In article <[EMAIL PROTECTED]>,
[EMAIL PROTECTED] (Dan Sugalski) wrote:
> At 12:25 PM + 3/12/04, Arthur Bergman wrote:
> >Hi,
> >
> >Tracking down test failures in ponie I noticed some tests using
> >SIGINT failing, they don't fail when I change the tests using
> >SIGUSR1, making me think t
In article <[EMAIL PROTECTED]>,
[EMAIL PROTECTED] (Mitchell N Charity) wrote:
> Leopold Toetsch <[EMAIL PROTECTED]> wrote:
>
>Marcus Holland-Moritz <[EMAIL PROTECTED]> wrote:
>
>> One of my modules embeds the ucpp preprocessor, which has a
>> function init_tables(). The same functio
On Fri, Mar 12, 2004 at 10:03:19AM -0500, Dan Sugalski wrote:
> At 6:06 PM -0500 3/11/04, Matt Greenwood wrote:
> >Hi all,
> > I have a newbie question. If the answer exists in a doc, just
> >point the way (I browsed the docs directory). What is the design
> >rationale for so many opcodes in pa
Stephane Peiry <[EMAIL PROTECTED]> wrote:
> This patch fixes a typo in the sun/sparc core.jit where
> the first Parrot_sub_n_nc should be Parrot_add_n_nc.
Thanks, applied.
leo
Arthur Bergman <[EMAIL PROTECTED]> wrote:
> I think all parrot externally visible macros, types and all functions
> should be prefixed Parrot_ as a start.
> Are patches welcome that change this?
Sure. But we should allow some already used prefixes too, beside Parrot_.
We have:
- Parrot_ API
-
On 15 Mar 2004, at 12:54, Leopold Toetsch wrote:
I think all parrot externally visible macros, types and all functions
should be prefixed Parrot_ as a start.
Are patches welcome that change this?
Sure. But we should allow some already used prefixes too, beside
Parrot_.
We have:
Cool, I still th
> [1] www.conmicro.cx/Hercules/
thanks for the info, although that link is broken. try instead:
http://www.conmicro.cx/hercules/
--jerry
**
This e-mail and any files transmitted with it may contain privileged or
confide
Arthur Bergman <[EMAIL PROTECTED]> wrote:
> PDB is too generic ParrotDB_
>> - PF_ PackFile
> ParrotPF , PF alone is already a taken prefix for Packet Filter if I
> don't recall wrong, not to mention the ancient define of PF_
>> - PackFile_ PackFile
> PackFile_ is too generic IMO too, and
Malte Ubl wrote:
> Dan Sugalski wrote:
> > So, if I understand this right (and I may well not), when you
> > instantiate a metaclass you get a class, and when you instantiate a
> > class you get an object, and since anything you instantiate is an object
> > anyway that means classes are objects.
PerlNum may not be handling -0.0 correctly.
This
new P0, .PerlNum
set P0, 0.0
print P0
print "\n"
set P0, -0.0
print P0
print "\n"
end
prints this
0
0
rather than say this
0
-0
For reference,
perl -e 'print -0.0,"\n"'
prints
-0
Thanks to ruby's test suite for the catc
On Mar 15, 2004, at 7:36 AM, Leopold Toetsch wrote:
Arthur Bergman <[EMAIL PROTECTED]> wrote:
PDB is too generic ParrotDB_
Of course, "ParrotDB" sounds like "Parrot database"
May be its best if someone who has commit privs just changes the
globals
and puts it in - its of not much help to se
On 15 Mar 2004, at 17:20, Jeff Clites wrote:
On Mar 15, 2004, at 7:36 AM, Leopold Toetsch wrote:
Arthur Bergman <[EMAIL PROTECTED]> wrote:
PDB is too generic ParrotDB_
Of course, "ParrotDB" sounds like "Parrot database"
May be its best if someone who has commit privs just changes the
globa
On Mon, 2004-03-15 at 04:26, Tim Bunce wrote:
> Is someone tracking the mailing list and adding questions and (good)
> answers into the FAQ?
Whoops, I'd planned to add this opcode question and answer to the FAQ
this weekend. Thanks for the reminder, Tim!
-- c
Hi,
the attached program aborts if run without without -G...
$ tar xzf err6.tgz
$ cd err6
$ ../parrot languages/EBNF/main.imc a.ebnf
'h' = code=1
'e' = code=1
'l' = code=1
'l' = code=1
'o' = code=1
'=' = code=4
a.ebnf:1:5 end of terminal 'hello'
a.ebnf:1:6 defining meta-identifier 'hello'...
'(*'
Here after is a patch that changes a "use warnings" into $^W = 1 in
order to be able to check perl 5.005
We then get:
$ perl ./tools/dev/parrotbench.pl -c ../parrot_bench.conf -b vpm\$
Numbers are relative to the first one. (lower is better)
p p-j p-C p5.5p5.8py
# New Ticket Created by Bernhard Schmalhofer
# Please include the string: [perl #27663]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org:80/rt3/Ticket/Display.html?id=27663 >
Hi,
this patch let's the URM compiler be called as 'perl ../urmc' in
'langua
$ perl ./tools/dev/parrotbench.pl -c ../parrot_bench.conf -b vpm\$
Numbers are relative to the first one. (lower is better)
p p-j p-C p5.5p5.8py rb
vpm 100%88% 99% 46% 91% - 58%
Attached is the missing python vpm, and a c
Hi,
the attached patch fixes null PMC dumping and adds a test for it.
jens
Index: t/pmc/dumper.t
===
RCS file: /cvs/public/parrot/t/pmc/dumper.t,v
retrieving revision 1.8
diff -u -r1.8 dumper.t
--- t/pmc/dumper.t 15 Mar 2004 08:03:25
Hi!
Sometimes, timer.t failes on tinderbox "colon (FreeBSD)".
Has anyone an idea what might be wrong?
On example:
t/pmc/timer.# Failed test (t/pmc/timer.t at line 152)
# got: 'ok 1
# ok 2
# ok 2
# ok 3
# '
# expected: 'ok 1
# ok 2
# ok 2
# ok 2
# ok 3
# '
# Looks like y
Under separate cover I've given Leo the current version of the Tcl
interpreter, hopefully he'll reply shortly that there were no problems
committing. =-)
Checked with a CVS checkout of a few minutes ago, all tests (still)
pass. (Thanks, Bernhard - the spirit of your patch is still there,
thoug
On Sun, Mar 14, 2004 at 02:32:44PM +0100, Leopold Toetsch wrote:
: Why? A ParrotClass is responsible for the method dispatch. The ParrotObject
: inherits that behavior.
In Perl 6 terms we'd prefer to say that ParrotClass "does" the
Dispatch role, and so does ParrotObject, but to call it inheritanc
docs/ops/rx.pod
perldoc (5.6.0) on OSX ironically stops at "The documentation for each
opcode follows"
perldoc (5.8.0) shows the whole pod.
I'm guessing this is a result of the '=head3' tags. Now, I did build
parrot with 5.8.0, but it's not the default perl, so by default, I get
the non-5.6 h
Going through my todo (hurm, should make TODO) list for Tcl, I'm
wondering:
- There's a sprintf opcode. Is there a way to do a scanf?
- is there an ETA on rx_compile? I hesitate to write my own RE compiler
having already dealt with tcl and tcl's [expr] ^_^
- Did exception handling ever get fix
> We should be able to get the linker to only expose our external entry
> points from libparrot. That way, we don't have to worry about the
> naming of API which isn't supposed to be called from outside. (If it
> works, it's simpler and safer than relying on a prefix.)
>
> JEff
# New Ticket Created by chromatic
# Please include the string: [perl #27671]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org:80/rt3/Ticket/Display.html?id=27671 >
Here's a patch summarized from Dan's post about the opcode explosion.
If there are no c
Mitchell N Charity <[EMAIL PROTECTED]> wrote:
> PerlNum may not be handling -0.0 correctly.
I do consider -0.0 as a bug ;)
> This
> new P0, .PerlNum
> set P0, 0.0
Both setting P0 to - or + zero has the same effect:
$ parrot -t 0.pasm
0 new P0, 35 - P0=NULL,
3 set P0, 0
On Mar 15, 2004, at 9:22 AM, Arthur Bergman wrote:
On 15 Mar 2004, at 17:20, Jeff Clites wrote:
We should be able to get the linker to only expose our external entry
points from libparrot. That way, we don't have to worry about the
naming of API which isn't supposed to be called from outside. (
On Monday, March 15, 2004, at 09:46 PM, Will Coleda wrote:
Feedback welcome. As are more patches. As would a pointer to a tcl
distro of the early 7 vintage whose test suite I might have a prayer
of passing a small portion of. =-)
Bad form to self-reply, I know, but I found the old distros at
Will Coleda <[EMAIL PROTECTED]> wrote:
> Going through my todo (hurm, should make TODO) list for Tcl, I'm
> wondering:
> - There's a sprintf opcode. Is there a way to do a scanf?
No not yet.
> - is there an ETA on rx_compile? I hesitate to write my own RE compiler
> having already dealt with tcl
Jens Rieks <[EMAIL PROTECTED]> wrote:
> Hi!
> Sometimes, timer.t failes on tinderbox "colon (FreeBSD)".
> Has anyone an idea what might be wrong?
The timer tests sleep in main for some time while a timer is supposed to
fire e.g. 3 times. I really don't know what happens if the system is very
bus
On Tuesday, March 16, 2004, at 02:01 AM, Leopold Toetsch wrote:
Will Coleda <[EMAIL PROTECTED]> wrote:
- Did exception handling ever get fixed? (I had submitted a test case
ages past - Last I saw was Leo saying "patches welcome". It was a COW
bug, IIRC.)
The COW bug is fixed. Using exceptions sh
On Mar 12, 2004, at 7:14 AM, Dan Sugalski wrote:
At 12:25 PM + 3/12/04, Arthur Bergman wrote:
Hi,
Tracking down test failures in ponie I noticed some tests using
SIGINT failing, they don't fail when I change the tests using
SIGUSR1, making me think that parrot somehow hijacks SIGINT but not
On 15 Mar 2004, at 17:25, Jeff Clites wrote:
We shouldn't, I would think, be snagging any signals unless user code
expresses an interest in the signal. The default disposition of every
signal is either to be ignored, or to abruptly terminate the process,
and we preserve that behavior if we just
At 5:27 PM + 3/15/04, Arthur Bergman wrote:
On 15 Mar 2004, at 17:25, Jeff Clites wrote:
We shouldn't, I would think, be snagging any signals unless user
code expresses an interest in the signal. The default disposition
of every signal is either to be ignored, or to abruptly terminate
the p
On Mar 15, 2004, at 9:30 AM, Dan Sugalski wrote:
At 5:27 PM + 3/15/04, Arthur Bergman wrote:
On 15 Mar 2004, at 17:25, Jeff Clites wrote:
We shouldn't, I would think, be snagging any signals unless user
code expresses an interest in the signal. The default disposition of
every signal is eit
Jeff Clites <[EMAIL PROTECTED]> wrote:
> But anyway, I thought the call to Parrot_sigaction(SIGINT, ...) inside
> of Parrot_init_signals() was just for testing purposes anyway.
It's currently of course for testing only, w/o much usage or even
correctness, and it's linux only for now. But - as Dan
Whilst trying to build ponie-2 on Solaris 8, I came across the following
issue: In order to use threads, both perl-5.[89].x and parrot need to
call some sort of yield() function.
In parrot, sched_yield is used; this function is available in the -lrt
library, so the solaris hints file adds that in
41 matches
Mail list logo
