in reply to memory penalty for loading XS modules?

Fast, small, correct. Pick two, if you're having a good day. Otherwise, be happy with one; some days you'll not get any.


the hatter

Replies are listed 'Best First'.
Re^2: memory penalty for loading XS modules?
by salva (Canon) on Jul 12, 2005 at 09:02 UTC
    do you really think so?

    IMHO small code is usually also fast and correct, it is when you start adding (unneeded) features that it becomes big, slow and buggy!