At first I'd assumed that if require'stdlib' couldn't find stdlib this was the tip of an iceberg. Bill explained the reason, from which I could guess that stdlib was the only j6 "require" argument apt to cause trouble in j7. This I have now verified to my satisfaction.
Eric's post set me straightaway looking for the bad examples I must have been copying. I'm compelled to conclude the problem is nowhere near as serious as I suspected and, failing corroboration from other releasers of code into the wild, I must adopt Eric's prescription. I apologise. On Sun, Dec 4, 2011 at 5:46 PM, Eric Iverson <eric.b.iver...@gmail.com> wrote: > Perhaps part of the confusion between you and Chris is that you should > never have had the sentence <require'stdlib'> in any version of J that used > the the standard profile. This bad sentence happened to have no effect in > J6, but that doesn't meet it deserves special treatment in J7. I think the > fix is for you to remove this bad sentence from all your scripts and then > move forward. > > On Sun, Dec 4, 2011 at 6:51 AM, Ian Clark <earthspo...@gmail.com> wrote: > >> It seems I've failed to make the point. Which I tried to make in the >> first sentence of my post. >> >> I can sympathize with developer reluctance to support obsolete >> constructs. If they come in droves they ruin the clean lines of a >> fresh start. Yes I can trawl through my code looking for stdlib. Yes I >> can write my own version of "require" to go in my startup.ijs. If that >> was all that was at stake it wouldn't have been worth posting about. >> But that won't do for code that's gone beyond my control. >> >> The question to ask ourselves is: are we keen to confine use of j7 to >> a brave band of pioneers, or do we want to promote it? A good way to >> achieve the former is to arrange for heritage code released in the >> wild to fail to load. >> >> On Sat, Dec 3, 2011 at 8:14 AM, chris burke <cbu...@jsoftware.com> wrote: >> >> I want to avoid maintaining different versions of scripts for j602 and >> j7 >> > as far as feasible. >> > >> > stdlib is loaded by default for both J6 and J7. You can safely remove >> > references to load or require it from both versions. >> > >> > On Sat, Dec 3, 2011 at 10:08 AM, Ian Clark <earthspo...@gmail.com> >> wrote: >> > >> >> > both verbs load and require come from stdlib, so that either it will >> >> fail... >> >> >> >> ...I see, whereas in j602 they were defined in jadefull.ijs . >> >> >> >> >why did you need it? >> >> >> >> Because scores of my scripts contain it, and will run unaltered >> >> otherwise. I'd rather not have to go changing (eg) >> >> require 'files stdlib' >> >> to: >> >> require 'files' NB. (I see that works in fact!) >> >> require '~system/main/stdlib.ijs' >> >> everywhere it occurs. I want to avoid maintaining different versions >> >> of scripts for j602 and j7 as far as feasible. >> >> >> >> Since stdlib can be taken for granted, I guess just to ignore it in >> >> require will suffice. >> >> >> >> >> >> On Sat, Dec 3, 2011 at 1:17 AM, bill lam <bbill....@gmail.com> wrote: >> >> > J7 could be changed to ignore instead of raise an error for it. >> However >> >> > both verbs load and require come from stdlib, so that either it will >> fail >> >> > or just a no-op, why did you need it? >> >> > >> >> > Сбт, 03 Дек 2011, Ian Clark писал(а): >> >> >> Can I offer a suggestion which would assist the porting of j602 code >> >> >> to j7 jhs? ... >> >> >> >> >> >> As it stands, >> >> >> require 'stdlib' >> >> >> -won't work in j7 jhs: it incorrectly locates: 'stdlib'. Ditto: >> >> >> require 'stdlib files' >> >> >> load 'stdlib' >> >> >> >> >> >> Can we have these idioms supported in j7 jhs as they are in j602 >> please? >> >> >> >> ---------------------------------------------------------------------- >> >> >> For information about J forums see >> http://www.jsoftware.com/forums.htm >> >> > >> >> > -- >> >> > regards, >> >> > ==================================================== >> >> > GPG key 1024D/4434BAB3 2008-08-24 >> >> > gpg --keyserver subkeys.pgp.net --recv-keys 4434BAB3 >> >> > ---------------------------------------------------------------------- >> >> > For information about J forums see >> http://www.jsoftware.com/forums.htm >> >> ---------------------------------------------------------------------- >> >> For information about J forums see http://www.jsoftware.com/forums.htm >> >> >> > ---------------------------------------------------------------------- >> > For information about J forums see http://www.jsoftware.com/forums.htm >> ---------------------------------------------------------------------- >> For information about J forums see http://www.jsoftware.com/forums.htm >> > ---------------------------------------------------------------------- > For information about J forums see http://www.jsoftware.com/forums.htm ---------------------------------------------------------------------- For information about J forums see http://www.jsoftware.com/forums.htm
