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
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,
Thomas Sandlaà wrote:
Int|Str <: Str && Str <: Int|Str && Int|Str <: Int && Int <: Int|Str
holds.
Uhh, I hardly believe that it was me writing that last night!
Int|Str is of course a proper supertype of Int and Str respectively.
So we really have: Str <: Str|Int && Int <: Str|Int, which warps us
Francois PERRAD <[EMAIL PROTECTED]> wrote:
>>$ perldoc -F docs/submissions.pod
> I tried to follow the documentation.
Works fine, thanks. Applied both.
> Francois.
leo
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
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
Selon Gabor Szabo <[EMAIL PROTECTED]>:
> > So I guess my question is, what exactly am I supposed to do to improve
> > test coverage? Am I supposed to modify the existing scripts so they
> > execute more functions exported by the module? Are any of the other
> > modules currently being tested not u
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
Larry Wall wrote:
On Sat, Mar 26, 2005 at 02:37:24PM -0600, Rod Adams wrote:
: How can you have a level independent position?
By not confusing positions with numbers. They're just pointers into
a particular string.
I'm not the Unicode guru but my understanding is that all composition
sequences are
[EMAIL PROTECTED] wrote:
Er, isn't that not just the wrong way around? The point is to do the
bookkeeping that an object is needed that does .meth() and that it
is stored in $a, and to complain when that is not the case when it
should be. The earlier the better.
I don't understand why writing 'my X
# 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
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
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
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
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
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
Miroslav Silovic wrote:
Remember, you can even change the class of instanced objects using
'does' (or 'but', but it'll at least copy the object). And as the
example above shows, this is statically intractable - it can happen in a
sub in a different autoloaded module.
Sorry this is a well establi
On Thu, Mar 31, 2005 at 06:35:06PM +0200, Thomas Sandlaß wrote:
: Is typing optional in the sense that it is no syntax error but
: otherwise ignored? To me this is pain but no gain :(
Well, you guys keep ignoring the answer. Let me put it a bit more
mathematically. The information in
my X $
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:
Hello,
I've been working on a Perl test suite for darcs, with notable recent
help from Schwern.
We used to have tests that looked like this:
like(`echo y | darcs command`,qr/$re/);
That would run the command and answer "y" to the first and only question
it asked. It worked well enough, but
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 Thu, 2005-03-31 at 11:51, Larry Wall wrote:
> my X $a;
>
> is *necessary* but not *sufficient* to do method existence testing in
> standard Perl 6 at compile time. You can do it IFF you have the class
> information AND the classes are willing to cooperate in your scheme.
> In the current
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
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
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
On Thu, 2005-03-31 at 13:11 -0500, Aaron Sherman wrote:
I can't answer most of these well. However...
> > One additional wrinkle is that *anyone* is allowed to declare a
> > class non-cooperative (open or non-final) during *any* part of the
> > compilation
>
> ... even after it is declared fina
I'd like to annotate Perl 6 parameters and other entities using
traits, since that's the best way (I know of) to have them appear
immediately in the text of the program where they are.
Supposing I had a "doc" trait, could I say:
sub f2c (Num $temp doc)
doc
{...}
Or would I be for
I'm no expert, but here's my take:
On Thu, Mar 31, 2005 at 01:11:37PM -0500, Aaron Sherman wrote:
> If you declare a variable to be of a type (let's even say a class to be
> specific), then you have hinted to the compiler as to the nature of that
> variable, but nothing is certain.
>
> That is to
On Thu, 2005-03-31 at 15:25, chromatic wrote:
> On Thu, 2005-03-31 at 13:11 -0500, Aaron Sherman wrote:
>
> I can't answer most of these well. However...
> Open-Closed is a great idea until the most natural and easiest way to do
> something is to to redefine a little bit of the world.
You seem
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 04:46:22PM +, Mark Stosberg wrote:
> We used to have tests that looked like this:
>
>like(`echo y | darcs command`,qr/$re/);
>
> That would run the command and answer "y" to the first and only question
> it asked. It worked well enough, but I looked for for a pure
Chip Salzenberg writes:
> I'd like to annotate Perl 6 parameters and other entities using
> traits, since that's the best way (I know of) to have them appear
> immediately in the text of the program where they are.
>
> Supposing I had a "doc" trait, could I say:
>
> sub f2c (Num $temp doc)
>
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
On Thu, 31 Mar 2005, Luke Palmer wrote:
Chip Salzenberg writes:
I'd like to annotate Perl 6 parameters and other entities using
traits, since that's the best way (I know of) to have them appear
immediately in the text of the program where they are.
Supposing I had a "doc" trait, could I say:
su
Make "is" polymorphic :D
Michael
On Thu, 31 Mar 2005 21:24:52 -0500 (EST), Abhijit Mahabal
<[EMAIL PROTECTED]> wrote:
> On Thu, 31 Mar 2005, Luke Palmer wrote:
>
> > Chip Salzenberg writes:
> >> I'd like to annotate Perl 6 parameters and other entities using
> >> traits, since that's the best w
On 2005-04-01, Michael G Schwern <[EMAIL PROTECTED]> wrote:
>> commands with Perl?
>
> When using open2 you have to be careful to close WRITE before you READ so
> the program does not hang waiting for more input. Once you've fixed that
> the technique above should be just fine.
>
> sub echo {
>
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:
Chip Salzenberg writes:
> I'd like to annotate Perl 6 parameters and other entities using
> traits, since that's the best way (I know of) to have them appear
> immediately in the text of the program where they are.
>
> Supposing I had a "doc" trait, could I say:
>
> sub f2c (Num $temp doc)
>
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
>
(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
On Fri, Apr 01, 2005 at 03:17:38AM +, Mark Stosberg wrote:
> > sub echo {
> > my($input, $command) = @_;
> >
> > local(*READ, *WRITE);
> > open2(*READ, *WRITE, "$DARCS $command";
> > print WRITE "a\n";
>
> Thanks for the tip. On this line, did you mean to write
>
>
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 <
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
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+
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
As I continue porting code to Perl 6, I found something else that the
synopsis don't seem to explain clearly.
What I want to be able to do is compare two references to see if they
point to the same thing, in this case an object, but in other cases
perhaps some other type of thing.
In synopsis
Darren Duncan wrote:
Now I seem to remember reading somewhere that '===' will do what I want,
but I'm now having trouble finding any mention of it.
So, what is the operator for reference comparison?
As someone who wrote a tool that uses refaddr() and 0+ in Perl 5 to
achieve the same thing, I agre
48 matches
Mail list logo
