I have an application that produces 4 J executables, used for different things (the application is management of quiz tournaments, and there is one application that runs individual matches, another to control the pairings etc, another to take contestants' pictures, and another to register teams as they arrive). There is much shared code between the executables, to ensure that file and communication formats are compatible.
I have all this in one directory, for convenience, because when I build the apps I build them all together & move them to the place where they all run on game day; also because they share so much code. I could split them, but that would be at least a minor nuisance. Henry Chris Burke wrote: > bill lam wrote: >> Normally I'll create a new directory for a new project. In case where >> two projects are otherwise identical but differs by only a few files, >> I'll put them into the same directory. > > This is the situation I wanted to avoid. The current design supports > more than one project in a directory. I myself have never used it, and > regard it as a nuisance. I am suggesting that there be at most one > project per directory - would this be a serious problem for you? > > > ---------------------------------------------------------------------- > For information about J forums see http://www.jsoftware.com/forums.htm > ---------------------------------------------------------------------- For information about J forums see http://www.jsoftware.com/forums.htm
