So what's your caching question then, if the answer isn't Memoize?

While I don't like myself the attitude that JavaFan is exhibiting throughout this thread (and elsewhere) I'd like to (try to) address your very question, which basically quite about everybody has also been asking here. For one thing, Memoize is a very generic tool: as such it uses a general technique, one which ought to work reasonably well in all cases. Namely, even if it has quite a lot of options, it basically stores cached parameters in a hash, whereas one may have a specialized (numeric) function that would benefit from memoizing into an array, and since caching is all about performance, this is one of those situations in which a relatively small efficiency gain (wrt the one of caching at all) would matter! The same can be said of generating and calling a wrapper sub, althought ISTR that the original one is then called through magic goto - it's still one more level of indirection.