# from David Irving # on Thursday 04 October 2007 18:28: >Since the two modules have a large number of dependencies, I would >rather only load the portion I need at runtime in order to save on >start-up time and memory use. However, PAR doesn't seem to pick up >all the necessary modules when I do this.
For most uses involving large modules and/or runtime issues, it is typically a win (on speed, accuracy, and clarity) to do your own dependency scanning with Module::ScanDeps (or etc) and feed an explicit list to pp. See e.g. http://svn.dotreader.com/svn/dotreader/trunk/inc (which is probably still down right now, but archive, google, or CPAN would have pretty good approximations of a recent dtRdrBuilder.pm.) It would be nice to have a tool (e.g. a Module::Build plugin) which checks timestamps and various other optimizations and formalizes this process into some ~yaml file (or set of files.) I'm not aware of such a thing though. --Eric -- We who cut mere stones must always be envisioning cathedrals. --Quarry worker's creed --------------------------------------------------- http://scratchcomputing.com ---------------------------------------------------
