Sunday 21 July 2002 21:34, Dan Sugalski wrote:
>
> No. They are not. You're missing the important case where the data
> structure is inherently and intrinsically multidimensional.
>
>my int Array @foo : dimensions(3);
>@foo[1;2;3] = 12;
>
> Or whatever the syntax is in perl to declare a 3
When a KEY * key datastructure is passed to a keyed method in array.pmc,
and key->next is true...:
array.pmc will recurse into the keyed lookup method of the PMC that it
contains, passing it key->next.
This implements the recursive indexing behavior as described in PDD08.
-scott
Index: parrot/
# New Ticket Created by Scott Walters
# Please include the string: [perl #15317]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt2/Ticket/Display.html?id=15317 >
When a KEY * key datastructure is passed to a keyed method in array.pmc,
and key->nex
On Mon, 22 Jul 2002, Angel Faus wrote:
> In my opinion, there are actually two different things to dicuss:
>
> - keyed opcodes
> - keyed methods on the PMC vtable
>
...
>
> Keyed opcodes can stay in the interest of code density.
>
> >
> > No. Keyed access for all methods stays. You're for
"Sean O'Rourke" <[EMAIL PROTECTED]> wrote:
> languages/perl6/README sort of hides it, but it does say that "If you have
> Perl <= 5.005_03, "$a += 3" may fail to parse." I guess we can upgrade
> that to "if you have < 5.6, you lose".
I notice that DBI no longer supports Perl releases <5.6. See
On Mon, Jul 22, 2002 at 11:14:15AM +0100, Sam Vilain wrote:
> "Sean O'Rourke" <[EMAIL PROTECTED]> wrote:
>
> > languages/perl6/README sort of hides it, but it does say that "If you have
> > Perl <= 5.005_03, "$a += 3" may fail to parse." I guess we can upgrade
> > that to "if you have < 5.6, you
My last mail didn't have many answers, maybe this one makes people think
and give ideas...
RFC: Hashing PMC's
Current PerlHash implementation accepts PMC's as keys, as long as they
can be transformed into Strings. While this can be enough for many
cases
On Mon, 22 Jul 2002, david nicol wrote:
>
> The thought process went something like this.
>
> In a world of distributed perl data, we want an
> expression like
>
> foreach (grep { $_->{smoker} and $_->{age} > 18 } @Subscribers){
> $->send($Cigarette_Advertisement)
> }
Hi
On http://natura.di.uminho.pt/~albie/parrot/ I have some documents I've
been working in about PMC's:
* Array PMC
* Perl Array PMC
* Perl Hash PMC
* Perl String PMC
* Writing a PMC
Regarding the first four, I would appreciate PMC programmers to read
them and give ideas/sug
# New Ticket Created by Leon Brocard
# Please include the string: [perl #15334]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt2/Ticket/Display.html?id=15334 >
The following patch makes imcc use the saveall and restoreall
ops (now that they're im
On Sun, Jul 21, 2002 at 02:05:42PM +, s. payrard @ wanadoo. fr wrote:
> # New Ticket Created by [EMAIL PROTECTED]
> # Please include the string: [perl #15267]
> # in the subject line of all future correspondence about this issue.
> # http://rt.perl.org/rt2/Ticket/Display.html?id=15267 >
>
Ashley Winters sent the following bits through the ether:
> Err, is this a bad time to ask where ParrotTuple is? :)
I think ParrotTuple would make a great first project for anyone who
wants to learn more about PMCs. It will also be fairly simple and
small, so if lots of docs were also included i
Nicholas Clark wrote:
> In October 2000 I believed that 5.005 maintenance *is* important for the
> acceptance of perl6, and I still do now:
Some minutes ago I sent a first patch to Sean, to make it work on 5.005_03.
One reason of failure is shown by the following snippet:
$ cat t1
#!/usr/bin/
# New Ticket Created by Aldo Calpini
# Please include the string: [perl #15335]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt2/Ticket/Display.html?id=15335 >
this little patch changes the 'print' debugger
command on PMC registers, so that it pr
Applied, thanks.
Daniel Grunblatt.
On Mon, 22 Jul 2002, Aldo Calpini wrote:
> # New Ticket Created by Aldo Calpini
> # Please include the string: [perl #15335]
> # in the subject line of all future correspondence about this issue.
> # http://rt.perl.org/rt2/Ticket/Display.html?id=15335 >
>
>
Leon Brocard wrote:
> I think ParrotTuple would make a great first project for anyone
> who wants to learn more about PMCs. It will also be fairly simple
> and small, so if lots of docs were also included it would make
> an ideal PMC to learn from in future. Any takers? ;-)
me, time permitting :-
On Mon, Jul 22, 2002 at 11:21:09AM +0100, Graham Barr wrote:
> On Mon, Jul 22, 2002 at 11:14:15AM +0100, Sam Vilain wrote:
> > "Sean O'Rourke" <[EMAIL PROTECTED]> wrote:
> >
> > > languages/perl6/README sort of hides it, but it does say that "If you have
> > > Perl <= 5.005_03, "$a += 3" may fail
Alberto writes:
> Finally, we need to hash PMC's. While I don't know what hash function
> we should use
Nor can you know, in the general case. Let PMCs hash themselves.
--
4.2BSD may not be a complete disaster, but it does a good job of emulating one.
On Mon, 2002-07-22 at 14:05, Simon Cozens wrote:
> Alberto writes:
> > Finally, we need to hash PMC's. While I don't know what hash function
> > we should use
>
> Nor can you know, in the general case. Let PMCs hash themselves.
This means one more function to the vtable!
The value returned by th
--- Leon Brocard <[EMAIL PROTECTED]> wrote:
> Ashley Winters sent the following bits through the
> ether:
>
> > Err, is this a bad time to ask where ParrotTuple
> is? :)
>
> I think ParrotTuple would make a great first project
> for anyone who wants to learn more about PMCs.
>Any takers? ;-)
this is a little tutorial about submitting patches
(should be added to a FAQ, or somewhere where it's handy
for people like me that tend to forget everything :-).
if there's something missing or incorrect, feel free to
let me know:
1. do a diff -u of the file(s) you want to patch
(note: Win32
Alberto Manuel Brandão Simões sent the following bits through the ether:
> This means one more function to the vtable!
FWIW every object in Java must implement a hashCode method:
http://java.sun.com/j2se/1.4/docs/api/java/lang/Object.html#hashCode()
Leon
--
Leon Brocard
# New Ticket Created by Alberto Manuel Brandão Simões
# Please include the string: [perl #15340]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt2/Ticket/Display.html?id=15340 >
While it can be thought as too simple and stupid PMC, it can be very
u
Tanton Gibbs sent the following bits through the ether:
> I implemented a RECALL preprocessor directive for the pmc classes.
> ...
> Thus ensuring that the correct semantics always occur.
I'm afraid I don't quite understand what RECALL is supposed to do.
Can you explain it in a little more detai
# New Ticket Created by Alberto Manuel Brandão Simões
# Please include the string: [perl #15345]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt2/Ticket/Display.html?id=15345 >
A simple way to generate assemble.pl constants initializaiton using
in
Dan, can we create this new vtable method? returning an integer (long
integer)... with name hashValue, or asHash.. or something else.
Alberto
On Mon, 2002-07-22 at 17:07, Leon Brocard wrote:
> Alberto Manuel Brandão Simões sent the following bits through the ether:
>
> > This means one more fun
On Fri, 2002-07-19 at 16:36, Melvin Smith wrote:
> Send me a complete patch and I'll put it in. I might rename the
> op to 'call'.
The attached patch makes the following changes:
- adds invoke op to core.ops (patch does not remove call and callco)
- adds vtable method 'invoke' to vtable.tbl
- ad
On 22 Jul 2002, Jonathan Sillito wrote:
> I had a small patch ready for docs/core_ops.pod, but I see that the file
> has been removed, so now I am not sure where to put the description of
> the invoke op.
Oh, no it hasn't... core_ops.pod is autogenerated from core.ops during
the build process
At 5:52 PM +0100 7/22/02, Alberto Manuel Brandão Simões wrote:
>Dan, can we create this new vtable method? returning an integer (long
>integer)... with name hashValue, or asHash.. or something else.
Yep. Call it id and have it return an INTVAL.
>On Mon, 2002-07-22 at 17:07, Leon Brocard wrote:
>
From: david nicol [EMAIL PROTECTED]
> foreach (grep { $_->{smoker} and $_->{age} > 18 } @Subscribers){
> $->send($Cigarette_Advertisement)
> }
>
> This would imply an extension of the array tieing
> interface, so we can send the grep block to the
> data server, and get b
Aldo Calpini sent the following bits through the ether:
> this is a little tutorial about submitting patches
> (should be added to a FAQ, or somewhere where it's handy
> for people like me that tend to forget everything :-).
This is really handy. While writing up the Perl 6 summary I've noticed
# New Ticket Created by Jonathan Sillito
# Please include the string: [perl #15347]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt2/Ticket/Display.html?id=15347 >
(apology: I read the nice tutorial on sending patches after I had
already sent this
Sure,
the basic problem is that in perlint.pmc we have something like:
void set_string( PMC* value ) {
CHANGE_TYPE( SELF, PerlString );
SELF->data = value->data
}
In other words implement a COW strategy after being changed into a
PerlString. However, in perlstring.pmc
the following is perf
On Mon, Jul 22, 2002 at 06:35:47PM +0100, Leon Brocard wrote:
> This is really handy. While writing up the Perl 6 summary I've noticed
> that there were a couple of patches which appear to have slipped
> though the gapes. Patch authors - if you follow the Parrot patch
> procedure we won't forget y
=head1 TITLE
Perl 6 summary for week ending 2002-07-21
=head1 AUTHOR
Leon Brocard <[EMAIL PROTECTED]>
=head1 DETAILS
Another week, another Perl 6 summary. Cunningly this week I have taken
over the summary from Piers in order to make it easier for me to
namecheck myself. It's been a good week
At 12:00 PM 7/22/2002 +0100, Nicholas Clark wrote:
>On Mon, Jul 22, 2002 at 11:21:09AM +0100, Graham Barr wrote:
> > On Mon, Jul 22, 2002 at 11:14:15AM +0100, Sam Vilain wrote:
> > > "Sean O'Rourke" <[EMAIL PROTECTED]> wrote:
> > >
> > > > languages/perl6/README sort of hides it, but it does say t
On Mon, Jul 22, 2002 at 01:12:57PM -0400, Dan Sugalski wrote:
> At 5:52 PM +0100 7/22/02, Alberto Manuel Brandão Simões wrote:
> >Dan, can we create this new vtable method? returning an integer (long
> >integer)... with name hashValue, or asHash.. or something else.
>
> Yep. Call it id and have i
On Mon, 22 Jul 2002, Dan Sugalski wrote:
> At 5:52 PM +0100 7/22/02, Alberto Manuel Brandão Simões wrote:
> >Dan, can we create this new vtable method? returning an integer (long
> >integer)... with name hashValue, or asHash.. or something else.
>
> Yep. Call it id and have it return an INTVAL.
Dan Sugalski:
# At 5:52 PM +0100 7/22/02, Alberto Manuel Brandão Simões wrote:
# >Dan, can we create this new vtable method? returning an
# integer (long
# >integer)... with name hashValue, or asHash.. or something else.
#
# Yep. Call it id and have it return an INTVAL.
Can we have it return a
# New Ticket Created by Simon Glover
# Please include the string: [perl #15357]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt2/Ticket/Display.html?id=15357 >
The file descriptors produced by the open op aren't compatible with
the ones require
# New Ticket Created by Angel Faus
# Please include the string: [perl #15358]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt2/Ticket/Display.html?id=15358 >
This patch apparently makes the rx engine behave well with the GC:
It creates a new pmc
On Sun, Jul 21, 2002 at 11:46:34AM -0700, Scott Walters wrote:
> Perl 5 runs *awesome* on a 486/25. Java (Kaffe) is completely unusable.
> AWT windows come up in a matter of *days*, whereas a Tk window comes up
> in about 45 seconds. On a fast computer, these things are blurred. The point
> is,
Nicholas Clark:
# On Sun, Jul 21, 2002 at 11:46:34AM -0700, Scott Walters wrote:
# > Perl 5 runs *awesome* on a 486/25. Java (Kaffe) is completely
# > unusable.
# > AWT windows come up in a matter of *days*, whereas a Tk
# window comes up
# > in about 45 seconds. On a fast computer, these thing
this is a little tutorial about submitting patches
(should be added to a FAQ, or somewhere where it's handy
for people like me that tends to forget everything :-).
if there's something missing or incorrect, feel free to
let me know:
1. do a diff -u of the file(s) you want to patch
(note: Win3
I will now demonstrate my ignorance of the parrot build system:
On Mon, Jul 22, 2002 at 04:23:08PM +, Alberto Manuel Brandão Simões wrote:
> Opefully, this can be accepted ;)
Do pmc files get turned pretty directly into C code?
Content-Description: boolean.pmc
> /* boolean.pmc
> * Copyri
I'm currently working on my Shishi parser/RE engine project, which
shares some similarities with what you'll need from the Perl 6 RE
engine. One thing that troubles me about it is that it's a
recursive-descent traversal across a state machine, and if you implement
this in C without a great deal o
On Mon, 22 Jul 2002, Nicholas Clark wrote:
> Do pmc files get turned pretty directly into C code?
Yes.
> > void set_bignum (PMC* value) {
> > /* XXX not sure if this can be optimized further safely */
> > // SELF->cache.struct_val = (DPOINTER*)value->vtable->get_bignum(INT
On Mon, 22 Jul 2002, Nicholas Clark wrote:
> I will now demonstrate my ignorance of the parrot build system:
>
>
> Do pmc files get turned pretty directly into C code?
>
Yes, via classes/pmc2c.pl. I don't see any code in there to replace the
// style comments, but I didn't read too careful
At 05:47 PM 7/22/2002 +0100, Nicholas Clark wrote:
> > Opefully, this can be accepted ;)
>
>Do pmc files get turned pretty directly into C code?
Yep.
>And if pmc files get turned pretty directly into C code, do the C++ style
>comments stay in there? If yes and yes, then the patch won't be accept
At 09:58 PM 7/22/2002 +0100, Nicholas Clark wrote:
>On Sun, Jul 21, 2002 at 11:46:34AM -0700, Scott Walters wrote:
> > Perl 5 runs *awesome* on a 486/25. Java (Kaffe) is completely unusable.
> > AWT windows come up in a matter of *days*, whereas a Tk window comes up
> > in about 45 seconds. On a f
At 07:45 PM 7/22/2002 -0400, Melvin Smith wrote:
>At 05:47 PM 7/22/2002 +0100, Nicholas Clark wrote:
>I think boolean is a language dependant thing and probably shouldn't
>be implemented as a PMC. For some languages, boolean can be optimized
>all the way down to the JIT level, and I'm not sure whi
51 matches
Mail list logo
