FW: Periodic Table of the Operators

2004-06-14 Thread Jared Rhine
[Rod == [EMAIL PROTECTED] on Sun, 13 Jun 2004 11:10:34 -0500] Jared> I haven't yet seen an example presented where using a Unicode Jared> operator would save keystrokes, for instance. Rod> That depends entirely on how you plan to generate them. If you Rod> are relying on a special command in your

Re: [perl #30230] [PATCH] add Fixed(Integer|Float|Boolean|String|PMC)Array classes

2004-06-14 Thread Leopold Toetsch
Dan Sugalski <[EMAIL PROTECTED]> wrote: > At 10:12 PM -0700 6/11/04, Matt Fowles (via RT) wrote: >>This patch adds the above Fixed*Array classes. They are basic tests for >>all of them included too, although more tests never hurts... > With MANIFEST patch even! Woohoo! > Applied, thanks. 1) Is

Re: Making PMCs

2004-06-14 Thread Dan Sugalski
At 12:53 PM -0500 6/13/04, Matt Fowles wrote: Nicholas~ I will try to answer what I can, based on my current experience making those array PMCs. Nicholas Clark wrote: a data pointer which I can use. I am always responsible for freeing anything there(?) and to do this I need to set

Re: [perl #30230] [PATCH] add Fixed(Integer|Float|Boolean|String|PMC)Array classes

2004-06-14 Thread Dan Sugalski
At 11:57 AM +0200 6/14/04, Leopold Toetsch wrote: Dan Sugalski <[EMAIL PROTECTED]> wrote: At 10:12 PM -0700 6/11/04, Matt Fowles (via RT) wrote: This patch adds the above Fixed*Array classes. They are basic tests for all of them included too, although more tests never hurts... With MANIFEST pat

Re: Making PMCs

2004-06-14 Thread Dan Sugalski
At 11:01 AM +0100 6/13/04, Nicholas Clark wrote: I'm trying to work out how to make PMCs. I'm not finding much documentation, and I'm not sure what I'm missing. Particularly I'm trying to work out where I'm allowed to store data, and what flags I might have to set I'll write up something more detai

Re: Making PMCs

2004-06-14 Thread Nicholas Clark
On Mon, Jun 14, 2004 at 08:53:10AM -0400, Dan Sugalski wrote: > At 12:53 PM -0500 6/13/04, Matt Fowles wrote: > >Nicholas~ > > > >I will try to answer what I can, based on my current experience > >making those array PMCs. > > > > > >Nicholas Clark wrote: > > > >>a data pointer > >>which I can

Re: Making PMCs

2004-06-14 Thread Dan Sugalski
At 2:33 PM +0100 6/14/04, Nicholas Clark wrote: On Mon, Jun 14, 2004 at 08:53:10AM -0400, Dan Sugalski wrote: At 12:53 PM -0500 6/13/04, Matt Fowles wrote: >Nicholas~ > >I will try to answer what I can, based on my current experience >making those array PMCs. > > >Nicholas Clark wrote: >

Re: Making PMCs

2004-06-14 Thread Leopold Toetsch
Nicholas Clark <[EMAIL PROTECTED]> wrote: > I'm trying to work out how to make PMCs. I'm not finding much documentation, I'll create a POD, which hopefully will answer all these questons. leo

Re: [perl #30245] [PATCH] Resizable*Array pmcs

2004-06-14 Thread Dan Sugalski
At 12:42 AM -0700 6/13/04, Matt Fowles (via RT) wrote: This patch adds Resizable*Array pmcs as the counterparts to Fixed*Array pmcs. It does so by inheriting from them, so the Fixed ones are changed too. Applied, thanks. -- Dan --

Re: [perl #30230] [PATCH] add Fixed(Integer|Float|Boolean|String|PMC)Array classes

2004-06-14 Thread Leopold Toetsch
Dan Sugalski wrote: At 11:57 AM +0200 6/14/04, Leopold Toetsch wrote: 1) Is there any good reason to start now malloc(3) based array classes? This leads to code duplication for all the utility vtable entries (like C). F can deal with all types already. list.c's pretty inefficient for most array us

Re: [perl #30230] [PATCH] add Fixed(Integer|Float|Boolean|String|PMC)Array classes

2004-06-14 Thread Dan Sugalski
At 4:56 PM +0200 6/14/04, Leopold Toetsch wrote: Dan Sugalski wrote: At 11:57 AM +0200 6/14/04, Leopold Toetsch wrote: 1) Is there any good reason to start now malloc(3) based array classes? This leads to code duplication for all the utility vtable entries (like C). F can deal with all types alread

Re: [perl #30252] [PATCH] work on languages/Makefile

2004-06-14 Thread Dan Sugalski
At 5:04 AM -0700 6/13/04, Bernhard Schmalhofer (via RT) wrote: I have been looking into languages/Makefile and tried to update and beautify it. Cool. Applied, thanks. -- Dan --it's like this--- Dan Sugalski

Re: [perl #30245] [PATCH] Resizable*Array pmcs

2004-06-14 Thread Leopold Toetsch
Dan Sugalski <[EMAIL PROTECTED]> wrote: > At 12:42 AM -0700 6/13/04, Matt Fowles (via RT) wrote: >>This patch adds Resizable*Array pmcs as the counterparts to Fixed*Array >>pmcs. It does so by inheriting from them, so the Fixed ones are changed >>too. > Applied, thanks. - duplicates existing PMC

More perl5.005 problems

2004-06-14 Thread Andy Dougherty
For some reason I haven't been able to figure out, perl5.00503 can't seem to handle the TODO test in t/pmc/object-meths.t. Here's the result of perl5.005 t/harness t/pmc/object-meths.t t/pmc/object-meths..FAILED test 19 Failed 1/21 tests, 95.24% okay Failed Test Status Wstat Total F

Re: [perl #30245] [PATCH] Resizable*Array pmcs

2004-06-14 Thread Dan Sugalski
At 5:50 PM +0200 6/14/04, Leopold Toetsch wrote: Dan Sugalski <[EMAIL PROTECTED]> wrote: At 12:42 AM -0700 6/13/04, Matt Fowles (via RT) wrote: This patch adds Resizable*Array pmcs as the counterparts to Fixed*Array pmcs. It does so by inheriting from them, so the Fixed ones are changed too. Ap

Slices and iterators

2004-06-14 Thread Dan Sugalski
Since we're going to need these, and I'm in a documenting and defining mood (yes, I am making a final decision on strings today. Whee!) I figure we need to tackle them. First, slices. Perl's got 'em, Python has them, Ruby, interestingly, doesn't. (Sort of) A slice is a subset of elements in an

The behaviour of iterators

2004-06-14 Thread Dan Sugalski
Once we decide how to *get* these things (see the previous e-mail) we need to decide how they should work. We can fiddle around, but honestly the scheme: 1) They act as arrays--if you want the 18th element in the iterator, access it directly 2) They have 'next', 'previous', 'first', 'last', and

Re: The behaviour of iterators

2004-06-14 Thread Matt Fowles
Dan~ Just a few questions. Dan Sugalski wrote: 2) They have 'next', 'previous', 'first', 'last', and 'reset' methods to get the next, previous, first, or last element in the iterator, or to reset the iterator to the beginning. Next, last, and reset change the internal current element pointer, fi

Re: The behaviour of iterators

2004-06-14 Thread Dan Sugalski
At 1:15 PM -0500 6/14/04, Matt Fowles wrote: Dan~ Just a few questions. Dan Sugalski wrote: 2) They have 'next', 'previous', 'first', 'last', and 'reset' methods to get the next, previous, first, or last element in the iterator, or to reset the iterator to the beginning. Next, last, and reset ch

Re: The behaviour of iterators

2004-06-14 Thread Luke Palmer
Dan Sugalski writes: > Once we decide how to *get* these things (see the previous e-mail) we > need to decide how they should work. We can fiddle around, but > honestly the scheme: > > 1) They act as arrays--if you want the 18th element in the iterator, > access it directly > 2) They have 'next

Re: Slices and iterators

2004-06-14 Thread Luke Palmer
Dan Sugalski writes: > The slice vtable entry should take as its parameter a slice pmc. This > should be an array of typed from/to values, so we can do something > like: > > @foo[0..2,4..8,12..]; > > with three entries in the slice array--one with a from/to of 0/2, one > with 4/8, and one

Re: The behaviour of iterators

2004-06-14 Thread Dan Sugalski
At 1:08 PM -0600 6/14/04, Luke Palmer wrote: Dan Sugalski writes: Once we decide how to *get* these things (see the previous e-mail) we need to decide how they should work. We can fiddle around, but honestly the scheme: 1) They act as arrays--if you want the 18th element in the iterator, acces

Re: Slices and iterators

2004-06-14 Thread Dan Sugalski
At 1:21 PM -0600 6/14/04, Luke Palmer wrote: Dan Sugalski writes: The slice vtable entry should take as its parameter a slice pmc. This should be an array of typed from/to values, so we can do something like: @foo[0..2,4..8,12..]; with three entries in the slice array--one with a from/to o

Re: Big nums

2004-06-14 Thread Dan Sugalski
At 8:15 PM +0100 6/14/04, Alex Gough wrote: [Sat, Jun 12, 2004 at 11:39:27AM +0200: [EMAIL PROTECTED] | Time for these as well. There's a partial implementation of them in | types/bignum.c. I think it's time to move that to src/ (and the | header file to .h) and get it integrated into parro

Re: Semantics of vector operations (Damian)

2004-06-14 Thread Damian Conway
Scott wrote: I'm just waiting for Damian to speak up :-) I'm not at all comfortable with the notion of junctions as lvalues. I've *always* considered a junction to be a special kind of constant, just as a number or a string or a reference is. I have trouble with junctive lvalues because I think t

Re: Big nums

2004-06-14 Thread Dan Sugalski
At 3:40 PM -0400 6/14/04, Dan Sugalski wrote: At 8:15 PM +0100 6/14/04, Alex Gough wrote: [Sat, Jun 12, 2004 at 11:39:27AM +0200: [EMAIL PROTECTED] | Time for these as well. There's a partial implementation of them in | types/bignum.c. I think it's time to move that to src/ (and the | heade

Re: Semantics of vector operations (Damian)

2004-06-14 Thread Austin Hastings
--- Damian Conway <[EMAIL PROTECTED]> wrote: > Date: Wed, 28 Jan 2004 12:34:15 +1100 > From: "Damian Conway" <[EMAIL PROTECTED]> Add to Address Book > To: "Language List" <[EMAIL PROTECTED]> >Subject: Re: Semantics of vector operations (Damian) Messages are *not* guaranteed to arrive in the

Characters/graphemes/freds

2004-06-14 Thread Dan Sugalski
Did we ever come to some consensus of what a "character" (that is a sequence of code points which makes up a single atomic thing in a language) should be called? I seem to remember grapheme being not-quite-correct, but I can't dig up the better answer. (And yes, the string doc is being finished

Strings. Finally.

2004-06-14 Thread Dan Sugalski
The official, 1.0, final version, modulo a more correct name for 'grapheme', or spelling/grammar errors. Do please note that whatever objection you may have to this has at least three people who disagree differently, and one or more (who aren't me) who agree with what you disagree with. Also no

Re: Big nums

2004-06-14 Thread Alex Gough
[Sat, Jun 12, 2004 at 11:39:27AM +0200: [EMAIL PROTECTED] > > | Time for these as well. There's a partial implementation of them in > | types/bignum.c. I think it's time to move that to src/ (and the > | header file to .h) and get it integrated into parrot. > > I'm not really sure if types

Re: More perl5.005 problems

2004-06-14 Thread Michael G Schwern
On Mon, Jun 14, 2004 at 12:00:42PM -0400, Andy Dougherty wrote: > For some reason I haven't been able to figure out, perl5.00503 can't seem > to handle the TODO test in t/pmc/object-meths.t. Here's the result of 5.5.3's Test::Harness doesn't know how to handle that style of TODO. You'll have to m

Re: More perl5.005 problems

2004-06-14 Thread Dan Sugalski
At 4:39 PM -0400 6/14/04, Michael G Schwern wrote: On Mon, Jun 14, 2004 at 12:00:42PM -0400, Andy Dougherty wrote: For some reason I haven't been able to figure out, perl5.00503 can't seem to handle the TODO test in t/pmc/object-meths.t. Here's the result of 5.5.3's Test::Harness doesn't know ho

Re: More perl5.005 problems

2004-06-14 Thread chromatic
On Mon, 2004-06-14 at 14:26, Dan Sugalski wrote: > >5.5.3's Test::Harness doesn't know how to handle that style of TODO. > >You'll have to make a dependency on T::H 2.x if you want to use TODO. > Is there another style of TODO that could be used here that would be > compatible with 5.005_03? No

Re: Semantics of vector operations (Damian)

2004-06-14 Thread Matthew Walton
Austin Hastings wrote: Perhaps we could consider the junctive lvalues as a sort of implied ?= operation: junction(@list) = value means unless junction(@list) == value { given junction { when 'none' { (@list.grep value) = undef; } when 'any' { for 0 .. random(@list) { @

Re: Semantics of vector operations (Damian)

2004-06-14 Thread Mark J. Reed
On 2004-06-14 at 22:58:58, Matthew Walton wrote: > 'it would be better to explicitly just say > > (@list.grep value) = undef > > although I think that might be supposed to be > > (@list.grep value) »= undef; Those do different things according to my understanding. The first removes all matchi

Re: Semantics of vector operations (Damian)

2004-06-14 Thread Matthew Walton
Mark J. Reed wrote: On 2004-06-14 at 22:58:58, Matthew Walton wrote: 'it would be better to explicitly just say (@list.grep value) = undef although I think that might be supposed to be (@list.grep value) »= undef; Those do different things according to my understanding. The first removes all matc

Parrot core dumps on FC1?

2004-06-14 Thread Michel Pelletier
Has anyone run into immediate core dumps on Fedora Core 1? When I run 'make' the interpreter successfully compiles, but dumps core when it tries to compile parrotlib.imc. : blib/lib/libparrot.a c++ -o parrot -Wl,-E -g imcc/main.o blib/lib/libparrot.a blib/lib/libicuuc.a blib/lib/libicudata.a -

Re: Semantics of vector operations (Damian)

2004-06-14 Thread George Woolley
Well, I'd speak up for intentionally allowing some silly alternatives except that's IMO unnecessary. With all the apparently-wonderful new possibilities which we'll soon have (OK, maybe not as soon as we'd like), it seems most likely that some will turn out to be silly. George "tim toady" On Mo

Some rationale for the mixed encoding scheme

2004-06-14 Thread Dan Sugalski
Since I know this is going to come up, I figure I should pre-empt it and be done with it. (Though I should've put this in the string document. Ah, well. Hopefully timing isn't everything, or I am *so* in trouble...) Why aren't we converting to Unicode on the edge? Since, after all, any Sane La

Re: Slices and iterators

2004-06-14 Thread Luke Palmer
Dan Sugalski writes: > At 1:21 PM -0600 6/14/04, Luke Palmer wrote: > >Dan Sugalski writes: > >> The slice vtable entry should take as its parameter a slice pmc. This > >> should be an array of typed from/to values, so we can do something > >> like: > >> > >> @foo[0..2,4..8,12..]; > >> > >> wit

Re: The behaviour of iterators

2004-06-14 Thread Luke Palmer
Dan Sugalski writes: > At 1:08 PM -0600 6/14/04, Luke Palmer wrote: > >Dan Sugalski writes: > >> Once we decide how to *get* these things (see the previous e-mail) we > >> need to decide how they should work. We can fiddle around, but > >> honestly the scheme: > >> > >> 1) They act as arrays--if yo

Re: Strings. Finally.

2004-06-14 Thread Brent 'Dax' Royal-Gordon
Sorry to reply to this, but I feel that this is a request for clarifications, not for a change. :^) Dan Sugalski wrote: Synthesized code points === ... becomes two integers, 0x0041 and 0x82A9. (Though it could represent them as 16-bit integers, since no character take

Re: Event design sketch

2004-06-14 Thread martin
On Tue, 11 May 2004, Uri Guttman wrote: > >> Why would alarm need any special opcode when it is just a timer > >> with a delay of [abs_time minus NOW]? > >> Let the coder handle that and lose the extra opcodes. > > mab> you want to make the latency between getting the abs_time, doing > ma