Don't forget about cache invalidation on dynamic method redefinition.
--
Mark Biggar
[EMAIL PROTECTED]
> Okay, so it's method cache time.
>
> First important note: I've never done this before (I think my
> antipathy towards objects might've given everyone just the tiniest
> clue :) so pointers to good docs and papers on this would be much
> appreciated.
>
> My current thinking, based entirely on the "Hmmm, if I had no clue
> there was any history here, what would I do?" school of design, is to
> do this:
>
> Method cache is an array of arrays of cache entries.
> This seems... too simple, so I'm sure I'm missing something besides
> the potential massive memory usage. So, by all means, have at it.
teddy bears get drunk
