Joe Tibollo wrote: > ... > The one big hole for me is something (a built in facility) for > managing locales. I like the J implementation of locales. > However, J could really benefit from having an explorer facility > similar to Dialog APL for managing locales. Something that would > display all locales and show their contents. Maybe that will > get added down the line. > ...
Some kind of session explorer would be useful, but there is not the same requirement for this as in APL. APL source is stored in an internal binary format, in the saved workspace. You can only browse through this by loading it into an APL session, and then examining what you have loaded - hence the need for an explorer. J source is stored in normal text files, like any other language. You can browse through this any way you like. Project Manager makes it particularly easy to do so. Applications are developed by working with the source files. Comparitively rarely do I want to go into the session and start poking around what has been loaded. Even then, it is usually just to look at some global variables, for which I can just enter their names or use a utility to list all globals. Working with source scripts rather than session objects is a key difference between J and APL. Note even the terminology - you refer to "managing locales", whereas I would think of managing scripts. ---------------------------------------------------------------------- For information about J forums see http://www.jsoftware.com/forums.htm
