William Coleda <[EMAIL PROTECTED]> wrote:
> (whoops)
> I just added octal and hex escapes to my local copy of the Tcl parser.
> I was working on unicode when I noticed that not all of the transcodes
> are done yet.
Yes, that's true. Much more work is needed still.
> This does not:
> $S0 = asc
Bob Rogers <[EMAIL PROTECTED]> wrote:
>From: Leopold Toetsch <[EMAIL PROTECTED]>
> ..., since I assume an
> Int+String=>Number method will exist that coerces the string to a number
> first. I imagine you could do this by creating a subclass of Int,
> e.g. LispInt, and then defining a LispInt+
Original Message
Subject: a warning and a failure for parrot in Tru64
Date: Thu, 31 Mar 2005 20:41:30 +0300
From: Jarkko Hietaniemi <[EMAIL PROTECTED]>
To: Leopold Toetsch <[EMAIL PROTECTED]>
cc: Warning: pylist.pmc, line 601: In this statement, the referenced
type of the pointer
Luke Palmer <[EMAIL PROTECTED]> wrote:
> Leopold Toetsch writes:
>> But with one more indirection a PIC-like scheme can work with
>> read-only bytecode too (probably). E.g. the assembler emits instead
>> of the proposed:
>>
>> infix "__add", Pd, Pl, Pr
>>
>> this opcode:
>>
>> infix (.MMD_ADD <
(whoops)
I just added octal and hex escapes to my local copy of the Tcl parser. I was
working on unicode when I noticed that not all of the transcodes are done yet.
This works:
$S0 = unicode:""
$S1 = chr 0x30b3
$S0 .= $S1
print $S0
print "\n"
This does not:
$S0 = ascii:""
$S1 = chr 0x30b3
From: Leopold Toetsch <[EMAIL PROTECTED]>
Date: Thu, 31 Mar 2005 09:38:15 +0200
Bob Rogers <[EMAIL PROTECTED]> wrote:
>From: Leopold Toetsch <[EMAIL PROTECTED]>
>Date: Wed, 30 Mar 2005 08:57:55 +0200
>
> ... , is that you are assuming (as I did not) that each and
>
I just added octal and hex escapes to my local copy of the Tcl parser. I
was working on unicode when I noticed that not all of the transcodes are done
yet.
This works:
At 05:57 PM 3/31/2005, Nigel Sandever wrote:
Is Parrot bytecode reentrant?
Yes.
That is, if I want to have two instances of a class in each of two
threads, will
the bytecode for the class need to be loaded twice?
No, just once.
Also, will it be possible to pass objects (handles/references) between
Is Parrot bytecode reentrant?
That is, if I want to have two instances of a class in each of two threads,
will
the bytecode for the class need to be loaded twice?
Also, will it be possible to pass objects (handles/references) between threads?
Thanks njs.
On Thu, Mar 31, 2005 at 05:45:12PM +0300, [EMAIL PROTECTED] wrote:
> Nicholas Clark wrote:
> >Autrijus Tang, the lead on the Pugs project, notes that an *unoptimised*
> >Parrot is already 30% faster than Haskell. Add compiler optimisation and a
> >few planned optimisations and Parrot will beat Pugs
Leopold Toetsch wrote:
> We gonna switch to SVN soon.
Lovely. :-)
> citing Chip:
> I think it would be a Good Thing for Parrot to live under Subversion
> rather than CVS. Just the change sets and rename tracking is enough
> reason, IMO.
I've been using SVN happily for almost a year now. It wor
Nicholas Clark wrote:
On Wed, Mar 30, 2005 at 03:26:36PM -0500, Jeff Horwitz wrote:
[snipped long response]
and let's not forget bytecode compatibility with all the non-perl
languages that will hopefully target parrot.
On Wed, Mar 30, 2005 at 03:49:54PM -0500, Aaron Sherman wrote:
On Wed, 2005-03
On Thu, 2005-03-31 at 12:04, Nicholas Clark wrote:
> Patches welcome, as I'm not sure of the best way to phrase the cross
> language stuff to follow on smoothly.
Also, Parrot provides access to Perl 6 from other languages and to those
other languages from Perl 6 at run-time, a feature which is bo
On Wed, Mar 30, 2005 at 03:26:36PM -0500, Jeff Horwitz wrote:
> [snipped long response]
>
> and let's not forget bytecode compatibility with all the non-perl
> languages that will hopefully target parrot.
On Wed, Mar 30, 2005 at 03:49:54PM -0500, Aaron Sherman wrote:
> On Wed, 2005-03-30 at 14:
Leopold Toetsch writes:
> But with one more indirection a PIC-like scheme can work with
> read-only bytecode too (probably). E.g. the assembler emits instead
> of the proposed:
>
> infix "__add", Pd, Pl, Pr
>
> this opcode:
>
> infix (.MMD_ADD << 24) | n, Pd, Pl, Pr
Just 256? Why don't you
Nicholas Clark wrote:
Autrijus Tang, the lead on the Pugs project, notes that an *unoptimised*
Parrot is already 30% faster than Haskell. Add compiler optimisation and a
few planned optimisations and Parrot will beat Pugs for speed hands down.
Autrijus things that Pugs could be made faster with som
Bob Rogers <[EMAIL PROTECTED]> wrote:
> The following trivial patch fixes this. It's written so that an
> explicit
> PARROT_TEST=0 make test
Thanks, applied.
leo
We gonna switch to SVN soon.
citing Chip:
I think it would be a Good Thing for Parrot to live under Subversion
rather than CVS. Just the change sets and rename tracking is enough
reason, IMO.
and:
Announcement should
also mention that we're not going to move icu over, so people should
download lib
Below inline/attached is a proposal to fix the MMD infix ops.
1) Again the infix ops - yes
>From a HLL point of view:
add d, l, r # PASM op
d = l + r # PIR syntax
d = l."__add"(r) # method call
d = "__add"(l, r) # Perl6 multi sub function cal
# New Ticket Created by Francois PERRAD
# Please include the string: [perl #34625]
# in the subject line of all future correspondence about this issue.
# https://rt.perl.org/rt3/Ticket/Display.html?id=34625 >
I add a new target 'setup' in the main Makefile.
That's allow the creation of a se
On Thursday 31 March 2005 11:47, Peter Sinnott wrote:
> Does that cover both the segmentation fault and the (I presume)incorect
> pasm that was being generated?
This covers only the segfault.
IMCC is known to produce incorrect pasm files, bug #32392.
jens
On Thu, Mar 31, 2005 at 11:44:01AM +0200, Leopold Toetsch wrote:
> Peter Sinnott <[EMAIL PROTECTED]> wrote:
>
> > Failed Test Stat Wstat Total Fail Failed List of Failed
> > ---
> > t/library/md5.t 4 10
Peter Sinnott <[EMAIL PROTECTED]> wrote:
> Failed Test Stat Wstat Total Fail Failed List of Failed
> ---
> t/library/md5.t 4 1024 44 100.00% 1-4
> t/pmc/mmd.t 6 1536186 33
Francois PERRAD <[EMAIL PROTECTED]> wrote:
>>$ perldoc -F docs/submissions.pod
> I tried to follow the documentation.
Works fine, thanks. Applied both.
> Francois.
leo
Nicholas Clark <[EMAIL PROTECTED]> wrote:
> With read only bytecode shared between processes, much of that "non-jit"
> resident memory is going to be shared. So much less swapping.
Yeah. Yesterday I wrote:
$ parrot -j -o order.pbc order.imc # emit jitted code
Well, that was rather wrong. But
Nicholas Clark <[EMAIL PROTECTED]> wrote:
> On Wed, Mar 30, 2005 at 09:11:51AM +0200, Leopold Toetsch wrote:
>> Bernhard Schmalhofer <[EMAIL PROTECTED]> wrote:
>> > +void freeze(visit_info *info) {
>> > +IMAGE_IO *io = info->image_io;
>> > +io->vtable->push_integer(INTERP,
Bob Rogers <[EMAIL PROTECTED]> wrote:
>From: Leopold Toetsch <[EMAIL PROTECTED]>
>Date: Wed, 30 Mar 2005 08:57:55 +0200
>
> ... , is that you are assuming (as I did not) that each and
> every language built on top of Parrot will define its own PMC classes,
> even for primitive arithmetic t
27 matches
Mail list logo
