>> It is not an issue at all if they more or less couldn't work >>without something doing the job of the other and few if any replacement >>options.
That's a strange point of view, I would love to see a good example of that. If you've got a system designed that way, then you've got bigger problems. IMO, tight coupling is the best way to complicate things, not the other way around. The point is, the default position should be to loosely couple your code unless you have good reason to do otherwise. The default position should not be to tightly couple your classes unless you see a reason to do otherwise. Jason Merrill Bank of America Global Learning Learning & Performance Soluions Join the Bank of America Flash Platform Community and visit our Instructional Technology Design Blog (note: these are for Bank of America employees only) _______________________________________________ Flashcoders mailing list Flashcoders@chattyfig.figleaf.com http://chattyfig.figleaf.com/mailman/listinfo/flashcoders
