I'm not worried about myself - I can deploy the correct version of my script for the system I am putting it on.
But that approach breaks down when there is more than one programmer. Suppose I need some package of Oleg's, and I have it as an .ijp file. Now, I can't move to 602 until I get an updated version of his package. The more popular J is, the worse the problem is. This problem is always with us when there are incompatible changes. I'm just saying that if 1!:45 could be quietly supported, the problem would disappear, and wouldn't that be nice? Henry Rich > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of Chris Burke > Sent: Friday, January 25, 2008 9:07 PM > To: Beta forum > Subject: Re: [Jbeta] Problem migrating a project to beta > > Henry Rich wrote: > > It seems there is more to the problem than I thought, as I found > > when I started fixing the next shortcut. Somehow it works > > without setting the 'Start In' field, which was blank all along. > > I'm not sure what the problem was, but I think it had to do with > > the changes to folder names introduced in the new release. > > > > The problem that got me into this mess is that > > when I use 602 to load the file built by 601 project manager, > > it fails on the line > > > > |domain error > > | rxdll=:'"',(_11}. 1!:45''),t,'" ' > > > > This goes away when I rebuild the project under 602. But > isn't it going > > to be a big problem if projects built under 601 won't run under 602? > > > > Perhaps 1!:45 should be supported but undocumented, so that > > projects that use regex will continue to run? > > I think it is best to match your build and J version - i.e. > build in 601 > if running in 601, and build in 602 if running in 602. With the J > directory changes from 601 to 602, you should be able to use the same > source scripts, and just make separate 601 and 602 builds. > > Alternatively, you could make copies of required DLLs such as regex in > the directory where 601 expects them. > > ---------------------------------------------------------------------- > For information about J forums see > http://www.jsoftware.com/forums.htm ---------------------------------------------------------------------- For information about J forums see http://www.jsoftware.com/forums.htm
