NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.
All the Perl that's Practical to Extract and Report
about I/O disciplines and I should retire to the Tassili-in-Aijer
mountains in Sahara as a camel herder :-)
-- Jarkko Hietaniemi
Stories, comments, journals, and other submissions on use Perl; are Copyright 1998-2006, their respective owners.
Launch from Moonbase Alpha (Score:1)
Very. Very. Cool.
So it's alpha, with large blinking warning signs to stay away, etc. Is the alpha flag a matter of concept (unsound/fragile) or a matter of effort (just not done yet)?
What's needed (if possible) to get it to a state so that people can use it?
Reply to This
Re: (Score:2)
Is the alpha flag a matter of concept (unsound/fragile) or a matter of effort (just not done yet)?
It might be fragile. So far it's holding up well, but I haven't done anything major with it and I'm wary of building this on top of so much scary tech. Devel::Declare has a few bugs (it causes the debugger to spin like a top) that I hope mst will clear up shortly.
Second is the prototyping syntax and behaviors. Since I'm creating, essentially, a new language feature here I'd like it to get knocked around some before locking it in place. I'm pretty happy with how it's come out, and if I stabilized with ju
Re: (Score:1)
On the matter of syntax, do you have any ideas on named arguments (i.e. hash/hash ref automatically unpacked into the variables)?
It seems doable to me. If the signature is misc vars, but you pass in a single hash ref, then... *magic*
Re: (Score:2)
While they are definitely a possibility, and you're not the first
person to ask for them, I'm wary of trying to mirror Perl 6's named parameters [perlcabal.org] right now for a number of reasons. First, they're not
necessary just now. Method::Signatures has a nice bag of problems to
deal with already and the signature syntax is extensible. And I
haven't given them a lot of thought.
Second, Perl 6 has all sorts of magic at the caller's end to force
named vs positional parameters. We have none of that. All we can do
is, as you