On Fri, Sep 06, 2002 at 11:27:59PM -0600, Luke Palmer wrote:
>
> Answering to the best of my knowledge.
>
> On Sat, 7 Sep 2002, Jonathan Scott Duff wrote:
>
> > Question #2:
> >
> > Why are we storing the hypothetical's sigil in the match object?
>
> I think it's to differentiate the different namespaces (scalar, array,
> hash) within the match object's hash. Personally, I don't like it, and
> think that people should just not do:
>
> / $var := <foo> , @var := <bar>* /
>
> Because it's dumb.
Related, I think: no-one answered my question about what happens when I
define
sub dumb ($var, @var) {
...
}
and then call it with the pair var=>$thing
It's ambiguous, because (if I understand perl6 correctly) arrays will auto
convert to array refs if required, so there's no simple way to decide which
parameter that ought to bind to.
Presumably for clarity it is better to store the sigil in the match object,
because if I've understood perl6 symbol tables correctly they are going to
be storing names-with-sigils. (To allow the elimination of typeglobs)
Nicholas Clark
--
Even better than the real thing: http://nms-cgi.sourceforge.net/
