Configure.pl doesn't work

2002-07-07 Thread Sebastian Bergmann
Fresh checkout on Linux: Checking MANIFEST...done. Setting up Configure's data structures...done. Checking for --miniparrot...done. Loading platform hints file...no hintsdone. Determining what C compiler and linker to use...done. Determining what types Parrot should use.

Suggestions

2002-07-07 Thread Bill Atkins
1. Perl6 should include a "has" and "have" keyword to set properties more clearly: my $var has Found; as opposed to: my $var is Found Similarly: my @list have Found I guess "have" sounds weird (all you base are belong to us ;) ) and may not be necessary. 2. Perl6 definitely should inclu

Re: Suggestions

2002-07-07 Thread Luke Palmer
On Sun, 7 Jul 2002, Bill Atkins wrote: > 1. Perl6 should include a "has" and "have" keyword to set properties > more clearly: Already been over this. Answer was no for some reason. > my $var has Found; See, then you need a direct object. I is it that C<$var has found>? :) (sortof) Seriously

Re: Perl 6 Summary

2002-07-07 Thread Dan Sugalski
At 11:03 AM -0600 7/7/02, Thom Boyer wrote: >And thanks for the pointers. I've been out of touch with the Perl >community the last couple of years. It's been exciting seeing how >Perl 6 is shaping up, but I'm having a hard time making up lost >time. The postings to perl6-language often take for

vtables and multimethod dispatch

2002-07-07 Thread Dan Sugalski
Okay, now that the dust from YAPC has settled and the holidays and such are done, it's time to get to some of the outstanding bits of Parrot. I'm going to get the extension mechanism designed over the next few days, but until then... We need a multimethod dispatch for vtable calls. Right now w

Re: what's new continued

2002-07-07 Thread Damian Conway
Ashley Winters asked: > > It *might* possibly work to hyper the constructor: > > > > my ($a, $b) = ^new Foo > > Would prefix ^ always return 'wanted' number of repetitions? Like a > smart C? This does bother me about the above proposed syntax/semantics. Hyperoperations take their "magnitud

[netlabs #769] [PATCH] let imcc use "if PMC, label"

2002-07-07 Thread Sean O'Rourke
# New Ticket Created by "Sean O'Rourke" # Please include the string: [netlabs #769] # in the subject line of all future correspondence about this issue. # http://bugs6.perl.org/rt2/Ticket/Display.html?id=769 > imcc currently only seems to support string and integer comparisons. This patch l

[netlabs #770] [PATCH] imcc strangeness

2002-07-07 Thread Sean O'Rourke
# New Ticket Created by "Sean O'Rourke" # Please include the string: [netlabs #770] # in the subject line of all future correspondence about this issue. # http://bugs6.perl.org/rt2/Ticket/Display.html?id=770 > simplify() was getting called with no arguments, but expecting one. I changed it

Re: vtables and multimethod dispatch

2002-07-07 Thread Sean O'Rourke
On Sun, 7 Jul 2002, Dan Sugalski wrote: > Basically what we need is a lookup matrix for each vtable method > (add, subtract, multiply, whatever) that we can index by left and > right types to get the actual method to call. I suppose resolution based on distance in number-of-args dimensional type

Re: vtables and multimethod dispatch

2002-07-07 Thread Dan Sugalski
At 2:08 PM -0700 7/7/02, Sean O'Rourke wrote: >On Sun, 7 Jul 2002, Dan Sugalski wrote: >> Basically what we need is a lookup matrix for each vtable method >> (add, subtract, multiply, whatever) that we can index by left and >> right types to get the actual method to call. > >I suppose resolutio

Re: vtables and multimethod dispatch

2002-07-07 Thread Dan Sugalski
At 2:08 PM -0700 7/7/02, Sean O'Rourke wrote: >On Sun, 7 Jul 2002, Dan Sugalski wrote: >> Basically what we need is a lookup matrix for each vtable method >> (add, subtract, multiply, whatever) that we can index by left and >> right types to get the actual method to call. > >I suppose resolutio

Re: what's new continued

2002-07-07 Thread Ashley Winters
On Sunday 07 July 2002 02:19 pm, Damian Conway wrote: > Ashley Winters asked: > > > It *might* possibly work to hyper the constructor: > > > > > > my ($a, $b) = ^new Foo > > > > Would prefix ^ always return 'wanted' number of repetitions? Like a > > smart C? > > This does bother me about the a

Re: what's new continued

2002-07-07 Thread Damian Conway
Ashley Winters wrote: > How about: > > $_ = new Doberman for my Dog ($spot, $rover) is rw; I don't think so. In Perl 6 you'd just need: $_ = new Doberman for $spot, $rover; Or, if you really did want that strong type-checking: for $spot, $rover -> Dog $dog is rw { $dog = ne

Re: what's new continued

2002-07-07 Thread Uri Guttman
> "DC" == Damian Conway <[EMAIL PROTECTED]> writes: DC> Ashley Winters wrote: >> How about: >> >> $_ = new Doberman for my Dog ($spot, $rover) is rw; DC> I don't think so. DC> In Perl 6 you'd just need: DC> $_ = new Doberman for $spot, $rover; will perl6 still support th

Synopsis 5 hits slashdot

2002-07-07 Thread Dan Sugalski
http://developers.slashdot.org/article.pl?sid=02/07/07/1646247 Standard slashdottish stuff--my favorite comment so far is the one wondering why Larry isn't contributing to Python development instead of redoing perl. -- Dan -

Re: what's new continued

2002-07-07 Thread Ashley Winters
On Sunday 07 July 2002 03:05 pm, Damian Conway wrote: > Ashley Winters wrote: > > How about: > > > > $_ = new Doberman for my Dog ($spot, $rover) is rw; > > I don't think so. > > In Perl 6 you'd just need: > > $_ = new Doberman for $spot, $rover; Hmm, I thought the for topic was made ro at

Re: what's new continued

2002-07-07 Thread Damian Conway
> will perl6 still support the indirect object syntax? i thought it was > going away and that would be: > > Doberman.new That works too, but the indirect object syntax isn't going away. TMTOWTDI, after all. > also is $_ an lvalue alias (topic) for $spot and $rover? Yep. Only *named* t

Re: what's new continued

2002-07-07 Thread Damian Conway
Ashley Winters wrote: > > $_ = new Doberman for $spot, $rover; > > Hmm, I thought the for topic was made ro at some point. Odd. Not the standard $_ topic. Only named topics default to read-only. > However, I still expect to be able to use my() in a loop condition/iterator > and have it

Re: what's new continued

2002-07-07 Thread Ashley Winters
On Sunday 07 July 2002 04:10 pm, Ashley Winters wrote: > > given my Doberman $sis is female = .dog[0] but pregnant -> $mother { > for my Doberman @puppies = new Doberman x $mother.littersize In hindsight, I probably meant for my Doberman @puppies = ^new Doberman x $mother.littersize It's

Re: what's new continued

2002-07-07 Thread Ashley Winters
On Sunday 07 July 2002 05:33 pm, Ashley Winters wrote: > my($foo, $bar) = for { $_ = new Stuff } Err, the parser would die if I did that, never mind. Can I have each, perhaps? *@foo = each { undef } I shouldn't be programming on Sunday, Ashley Winters

Re: [netlabs #769] [PATCH] let imcc use "if PMC, label"

2002-07-07 Thread Melvin Smith
At 05:01 PM 7/7/2002 -0400, via RT wrote: ># New Ticket Created by "Sean O'Rourke" ># Please include the string: [netlabs #769] ># in the subject line of all future correspondence about this issue. ># http://bugs6.perl.org/rt2/Ticket/Display.html?id=769 > > > >imcc currently only seems to suppor

Re: init_method_t for coroutines and subs?

2002-07-07 Thread Melvin Smith
At 08:55 AM 7/5/2002 -0500, David M. Lloyd wrote: >On Wed, 3 Jul 2002, Melvin Smith wrote: > > > At 09:51 PM 7/3/2002 -0400, Josh Wilmes wrote: > > >I know there was some talk about this extra "address" parameter recently, > > >but i'm not sure what the upshot of it is. Right now, tcc is complain

Re: init_method_t for coroutines and subs?

2002-07-07 Thread Melvin Smith
At 12:48 PM 7/5/2002 -0400, Dan Sugalski wrote: >At 10:39 PM -0400 7/3/02, Melvin Smith wrote: >>At 09:51 PM 7/3/2002 -0400, Josh Wilmes wrote: >>>I know there was some talk about this extra "address" parameter recently, >>>but i'm not sure what the upshot of it is. Right now, tcc is complaining

Re: vtables and multimethod dispatch

2002-07-07 Thread Mike Lambert
> We need a multimethod dispatch for vtable calls. Right now we're > working on a "left side wins" scheme and, while we're going to keep > that (sort of) we really need a way to choose the method to call > based on the types on both sides of binary operators. (Unary > operators, luckily, are easie