At 12:51 PM 8/5/00 -0400, Ken Fox wrote:
>Dan Sugalski wrote:
> > but it's really not SVs that eat up all the space, it's arrays and hashes.
>
>And closures! If curried functions get added (and they're just sugar for
>closures) we're going to have to optimize them a *lot* more than Perl 5.
What, in closures, eats all the space now? (I ask as I've not looked)
> > Three classes, which is why the three lines here. I'm picturing a very
> > simple, probably not too fast, high-level interface for embedding apps, a
> > reasonably fast, middle level for extensions that's still protected from
> > change, and a low-level, fast interface for op type stuff that has intimate
> > knowledge of the guts.
>
>When we document this, can we move the low level interfaces out of the
>pod directory? It would be a shame to have people accidentally start using
>the internal interfaces just because they're well documented. ;) (And if
>we say something like "this is fast" people will ignore all the warnings.)
It'll have to be documented somewhere, so I don't forget if nothing else.
Where it goes in the distribution is a separate issue.
(PerlHereThereBeDragons.pod, anyone? :)
Dan
--------------------------------------"it's like this"-------------------
Dan Sugalski even samurai
[EMAIL PROTECTED] have teddy bears and even
teddy bears get drunk
