Thanks for the tip - its something I will definitely explore. My entire
gripe with this problem has not been with performance or efficiency but with
readability and easy maintainability of the many scripts in our main
application - but we are getting there - and the great thing is there are so
many options.
Our current proprietary system (which embeds a C/BASIC type language in the
HTML pages) doesn't scale well no matter how much hardware we throw at it,
but has the benefit of having all the "messy" stuff like middleware and
database connections, session handling etc. hidden away. It will be a case
of culture shock for the developers to suddenly have to explicity include
all the modules they need and perform all the initialisation stuff - so we
are trying to make it as simple as possible to migrate, without a large
increase in the size of the scripts.
> Are you using OO perl and inheritance? I'm late on this thread, but what
> about use'ing a common module which then use'es all the other modules
> you need? It's well worth the effort IMHO...
> > I realise the actual code isn't duplicated - but the script itself
still
> > needs the list of "use" directives regardless of whether you pre-load
them
> > and there doesn't seem to be an easy way to factor this common block of
> > unsightly directives out into one file for use in multiple scripts that
> > share the same resources.
