On Mon, Aug 25, 2008 at 12:00 PM, Philip A. Viton <[EMAIL PROTECTED]> wrote: > Any suggestions?
It's been quite some time since I had to deal with such things, but I have worked with parameter collections that were bunches of name/value pairs with some of the being optional and also supporting the inclusion of names and values which will be ignored by the routine in question. In my experience, systems that complex tend to be hard to understand and really need some good documentation which cuts across the layers of abstraction in several different ways. Also, I found myself writing routines to deal with issues like providing default values for everything that needs a default, and for extracting just a named list of variables from a package of names and values. This approach does simplify the upgrade process, when one small part of the system needs to be changed and the rest does not need to be changed. But finding what values are actually being used (and where, and why) will become difficult unless some serious out-of-band effort goes into tracking that kind of information. FYI, -- Raul ---------------------------------------------------------------------- For information about J forums see http://www.jsoftware.com/forums.htm
