Joe Tibollo wrote: > I don't think it is all that trivial. > > Ideally, it would be nice to save everything in the workspace and reload > it with a simple > ")save" and ")load" . Having to write a function to query all locales > and package all objects to a single file is a serious undertaking - > perhaps that is why it still has yet to be done...
The bottom line is that J code is saved in scripts, and not in workspaces. If you want to use J, you must learn to work with scripts. If instead you want to duplicate your APL workspaces in J, good luck to you, but you will get no sympathy from the J team. Very early versions of J had saved workspaces, but they were removed when it was realized that scripts work better. Once you become familiar with the J IDE, you won't miss the workspace. There are serious drawbacks to saving source in an internal binary format like the APL workspace. Examples: you need special editors and the appropriate interpreter otherwise the source is unreadable, and need explicit )LOAD and )SAVE. It is awkward to update definitions stored in more than one workspace. It needs custom source code managers - APL is the only language where experienced programmers put a lot of effort into writing their own. ---------------------------------------------------------------------- For information about J forums see http://www.jsoftware.com/forums.htm
