> Why push it through a user subroutine. Might as well make it part of the
   > core language.

Why exacerbate the core, when I one-line user sub can do it?


   > Why add another keyword non_lazy. though it isn't an antonym, eval{}
   > has the right meaning and effect.

No, "non-lazy" was just some ordinary subroutine that I was enervating an
argument for. It certainly isn't part of the proposal.

   > I can see the utility of having the callee specify the alacrity of the
   > parameter. But this would put quite a burden on the parser/runtime engine.
   > 
   > Package A and B both define a function foo. A->foo has non-lazy arguments
   > B->foo has lazy arguments. Then
   > 
   >    $fooA = new A;
   >    $fooB = new B;
   > 
   >    $fooA->foo ....
   >    $fooB->foo ....
   > 
   > What is a poor perl parser to do?

Ignore the prototype unless $fooA and $fooB are typed lexicals.
I.e. act just like it does now.

Damian

Reply via email to