I am hoping that I am not misunderstanding the PM "stand alone" script but here goes...
Ever since I've started using PM to build my projects, I have been dependent on this "feature" of J. All my projects only distributes J.EXE, J.DLL and the corresponding IJS file. When you open the IJS file, the standalone script occupies 80 to 90 percent of the code and more than half of this code unused. When I was trying to integrate the JDB add-on to one of my project, I was having problems with conflicts between the add-ons that are not apparent during build but will only come up if during runtime. Right now I don't know the extent of the impact to my code if the standalone scripts where decommitted and I don't have a good suggestions on this but I am interested on what's going to be the end product. -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Sherlock, Ric Sent: Thursday, October 15, 2009 10:14 AM To: Beta forum Subject: Re: [Jbeta] decommit standalone script I'm thinking that even if standalone script logic was decommitted, it would still be nice to have some sort of tool for listing the dependencies of a script or project? > From: bill lam > > One reason why code in PM is so complicated is the requirement to > build standalone script. But it is, as now, still incomplete in that > only J base library can be handled, all other script including addon > cannot. ---------------------------------------------------------------------- For information about J forums see http://www.jsoftware.com/forums.htm ---------------------------------------------------------------------- For information about J forums see http://www.jsoftware.com/forums.htm
