At 1:49 PM -0700 6/14/02, Larry Wall wrote:
>On Fri, 14 Jun 2002, Nicholas Clark wrote:
>: Or would the property of "I don't use caller or want" still be useful on a
>: subroutine, because the run-time could determine that it would be
>: inline-able (or whatever) inside a loop at run time, based on parameters
>: passed to it? (and call it non-inline if the parameters were not base perl
>: types)
>
>Maybe. I'm not an expert on run-time optimizations. I just know that
>the more info you have, the easier it is to know when you can get
>away with a particular optimization. And that there are advantages
>and disadvantages to knowing anything at any particular stage. And I
>really like optional declarations, because then the programmer gets
>to make the tradeoff.
There's also the problem of active data--does a variable's
tie/overload functions have access to their calling stack? If so,
it's doubly hard to figure out whether there's anything that may
inspect the call stack.
--
Dan
--------------------------------------"it's like this"-------------------
Dan Sugalski even samurai
[EMAIL PROTECTED] have teddy bears and even
teddy bears get drunk
