|
I've seen situations where each function was in its own include file; every function that called others used include_once() to load just those other functions. I don't know how good an idea that is in general: it was being used in a situation where standalone apps were being generated from the code in the library, and it was necessary that only the code that was actually used in any given application would be included. There was also a tool for tracking these include() dependencies.
__________________
On two occasions I have been asked [by Members of Parliament], "Pray, Mr. Babbage, if you put into the machine wrong figures, will the right answers come out?" I am not able rightly to apprehend the kind of confusion of ideas that could provoke such a question.
Last edited by Weedpacket; 02-21-2004 at 08:48 PM.
|