Posted by Tom Fulton on June 27, 2005 at 12:15:27:
Getting deeper into our Win Programming redevelopment project, we've run across something that I'd like to clarify. Using the HowTo project from
Las Vegas as an example, file HowTo.Inc is developed that generates SET
statements so that individual controls are easily reference by names
that are meaningful. My question is - Why is there only one .INC file
for the entire project as opposed to individual .INC files by dialog?
As we generate new Windows programs from existing versions we find that
contols defined in other dialogs can be reference in the new program, with its own set of controls, and no compile error is generated. The compile errors would be an efficient means of clearing out unused code
when copying into new programs. As it is, one must either leave the code that doesn't apply or search out each name to see if it applies.
Is there a downside to individual .INC files other than the fact that a project may wind up with a couple hundred .INCs as opposed to one, single large .INC?