Oleg Kobchenko wrote: > With this regard, I have some critique on the > Project based approach in J: the sources are small > managable code units, grouped nicely into folders. > But when built it all is packed into the same > single locale. So the principle of modularity is > compromized: to be able to communicate within the > single class, code from different code units need > to access private parts of other units. This is similar > to the problem with globals only in locale scope.
J does not enforce this organization, and perhaps the problem here is the term "project". In Project Manager, a project refers to a single source directory, which is normally intended to be loaded into a single locale. A sizeable application would normally be built from several projects, each loading into its own locale. A save function might build a single script to load the application, but there is no problem in one script populating several locales. ---------------------------------------------------------------------- For information about J forums see http://www.jsoftware.com/forums.htm
