I suggest reading the file when you have access and then using a temp file later on when you need to load it. This is an adequate workaround to what has always been a kludgey area.
It is unlikely that Jsoftware has interest in 'bug fixes' in this particular area. We will likely, by year end, do a new official GPL release of J that will be intended for broader use (and feedback to us). One change we will make is that we will distribute the source file that implements our official release lock/unlock mechanism. This change will be accompanied by doc changes that state that locked files are not very secure (never were and will be even less so). Locking a file is an indication that the J source in the file is proprietary and that nice users will respect that and not pry. And nasty users are just nasty. On Thu, Oct 22, 2015 at 12:40 PM, Thomas Costigliola <[email protected]> wrote: > Attempting to run a locked script from a noun doesn't work: > > 0!:1]3!:6 'sum=:+/' > > � > > |spelling error > > | � > > > I understand there might not have been an apparent use case for this, but > is there a technical or security reason for the restriction? > > > I need to read the contents of a locked script into a noun but not execute > it until a later time at which the file will no longer be accessible. This > seems easy to implement in the interpreter, but I was wondering if there > was something I am overlooking that makes it difficult or undesirable. > ---------------------------------------------------------------------- > For information about J forums see http://www.jsoftware.com/forums.htm ---------------------------------------------------------------------- For information about J forums see http://www.jsoftware.com/forums.htm
