At 05:34 PM 8/1/00 -0400, John Tobey wrote:
>Dan Sugalski <[EMAIL PROTECTED]> wrote:
> > ) Compaq C
> > will do it differently depending on the number of times that the inlined
> > function is used.
>
>Okay. For starters, assume that every inline function is called in
>exactly one place in the translation unit that defines its non-inline
>counterpart. That one place being, of course, i_foo's foo. This is a
>natural result of a clean, PI-like-generated source.
Bad assumption. How often is av_fill called?
Also, these functions are the *internal* functions. The external ones (i.e.
what modules and embedding programs use) will *not* be inline. They will
all be well-defined calls into the perl core shared library. There won't be
any macros, or inlines, or any of that stuff. No direct access to guts at
all--when perl passes you an SV *, it's a bloody magic cookie and you
shouldn't touch. We may well change how they're structured, but the
interface will be fixed and solid. (Expanded upon, perhaps, but that's it)
Modules built against perl 6.0.1 should run when you upgrade and swap in
6.8.5. (Or when your app with embedded perl gets a new perl swapped in on
it) No relinking or rebuilding required, even if we gut and redo how
scalars are implemented.
Whether this happens is another matter, but I'm darned well going to try.
Dan
--------------------------------------"it's like this"-------------------
Dan Sugalski even samurai
[EMAIL PROTECTED] have teddy bears and even
teddy bears get drunk
