Time to change the (perl 6) guard!

2004-07-06 Thread Dan Sugalski
Or at least lay on more. Here's the scoop--we need a Perl 6 pumpking,
someone to take on the responsibility of making the Perl 6 compiler
happen. When we started this whole process these many years ago, we
though having one person handle the software end of things was
sufficient, but making perl 6 a reality is a much larger task than we'd
originally figured, as both Perl 6 the language and Parrot the
interpreter have ended up bigger than we'd thought they'd be. Bigger,
in fact, than one person can reasonably manage, especially with a
volunteer project.
Hence, the call. Got people skills? Can you organize? Competently
*design* code? Got free time?  Work with people who are, well, Larry?
Cool, this is for you. You don't have to be a star programmer, nor a
parser or compiler whiz, though that certainly won't hurt.
Enthusiasm's what you need, as there are people willing to help you
out with the rest.
There are plenty of things you don't have to worry about. You don't
have to worry about the language design--that's Larry's job. Nor do
you have to worry about the interpreter engine--that's Dan's
job. What you'll have to do is get the Perl 6 compiler module, and
its standard library, designed and implemented.
It's a big job, but someone has to do it, and that someone could be
you. (As a bonus, you get your own Secret Perl Cabal membership card
and Decoder ring!) If you're interested, make your pitch to our
esteemed, and mostly sane, Perl 6 manager-type person Allison Randal,
at [EMAIL PROTECTED]
Good luck!
--
Dan
--it's like this---
Dan Sugalski  even samurai
[EMAIL PROTECTED] have teddy bears and even
  teddy bears get drunk


Re: Time to change the (perl 6) guard!

2004-07-06 Thread Austin Hastings
--- Dan Sugalski [EMAIL PROTECTED] wrote:
 we need a Perl 6 pumpking,

Luke Palmer.


Re: Time to change the (perl 6) guard!

2004-07-06 Thread Dan Sugalski
At 6:21 AM -0700 7/6/04, Austin Hastings wrote:
--- Dan Sugalski [EMAIL PROTECTED] wrote:
 we need a Perl 6 pumpking,
Luke Palmer.
No fair volunteering other people, though I'd be happy to forward 
*your* volunteering on to Allison... :-P
--
Dan

--it's like this---
Dan Sugalski  even samurai
[EMAIL PROTECTED] have teddy bears and even
  teddy bears get drunk


Re: Time to change the (perl 6) guard!

2004-07-06 Thread Austin Hastings
--- Dan Sugalski [EMAIL PROTECTED] wrote:
 At 6:21 AM -0700 7/6/04, Austin Hastings wrote:
 --- Dan Sugalski [EMAIL PROTECTED] wrote:
   we need a Perl 6 pumpking,
 
 Luke Palmer.
 
 No fair volunteering other people,

Don't think of it as volunteering other people so much as popular
acclaim. 

 though I'd be happy to forward 
 *your* volunteering on to Allison... :-P

Of the qualities you listed for Pumpking:

Look, I already told you! I deal with the goddamn customers so the
engineers don't have to! I have people skills! I am good at dealing
with people! Can't you understand that? What the hell is wrong with you
people?

=Austin



Re: fast question

2004-07-06 Thread Luke Palmer
Matija Papec writes:
 
 Would there be a way to still use simple unquoted hash keys like in old 
 days ($hash{MYKEY})?
 
 imho %hashMYKEY at first sight resembles alien ship from 
 Independence day. :)

Of course there's a way to do it.  This is one of those decisions that I
was against for the longest time, until one day something clicked and it
made sense.

So I can certainly understand why you don't like it.

You might do it something like this:

macro postcircumfix:{} ($base, $subscript)
is parsed( / $?subscript := (\w+) /)
{
return { $base.{$subscript} }
}

Whether that actually works depends on whether macros are applied until
one Cis parsed matches.  If not, then you'll have to do it some other
way:

macro postcircumfix:{} ($base, $subscript)
{
if $subscript.text ~~ /^ \w+ $/ {
return { $base.{$subscript} };
}
else {
no macros 'postcircumfix:{}';  # make sure this isn't
   # interpreted by the macro
return { $base.{$subscript} };
}
}

Luke


Predeclaration of subs

2004-07-06 Thread Luke Palmer
Considering that:

$obj.meth foo;

No longer needs parentheses, and that argument processing is done on the
callee rather than the caller side (well, most of the time), do I still
have to predeclare Cfoo if I want to say:

foo bar, baz;

?

Also, how does:

method evil($x is rw)

Work if argument processing is done on the callee side and we want to
avoid constructing lvalues out of everything?

Luke