Bill Zielenbach wrote: > I'd like to only include the functions that are called by the > program, but > realize there are tradeoffs in convenience vs. compiled size > efficiency. Unused functions are removed at link time, if you have 'Strip unused code' turned on (the default and recommended setting). The only disadvantage of unused functions is that they slow the build. You may find it better to take a (possibly small) build-time hit instead of complicating your include arrangements. > I have the > impression that under this new approach, all the files that I intend > to > include in the project have to be placed within the project folder. Yes. > Do 2 > projects using the same function need identical copies of that > function in > each folder, or will an alias suffice, so that the function file could > remain in the outer MP Programming folder that contains the two > project > folders and be maintained/updated in one place only? Create a Finder alias for each include file, drag a copy of the alias to each project folder and add the alias to each project window. Then you don't have to maintain multiple copies of the source. > Further, would the FSRef for the application's folder now refer to the > project folder or the outer MP programming folder? That affects how > I refer > to files that transfer results between programs and which currently > reside > in the outer MP Programming folder. The application's folder is the folder that contains the app. Immediately after a build, Xxxxx.app appears alongside Xxxxx.fbproj, i.e. the application's folder is the project folder. Robert P.