Re: [Bug-apl] Why disable ⍎')load WS'?

[Juergen Sauermann]

Hi Blake, fixed in SVN 510. Expect surprises. /// Jürgen On 11/15/2014 05:33 PM, Blake McBride wrote: Dear Juergen, Having )LOAD kill the function that executed it is expected.  ⍎')LOAD ws' should act exactly the same as typing:     )LOAD ws from any point.  In other words )SI doesn't matter and what function it was in doesn't matter.  Just like any )LOAD, all that information is lost. Again, having this is real helpful because you can have a startup WS present a menu of available applications and then have the right one loaded upon user selection.  Without this feature, the user may have to know some APL. Obviously, this will have to be special cased in execute. )COPY doesn't work in this scenario for obvious reasons. If and when you get the chance.... Thanks. Blake On Sat, Nov 15, 2014 at 7:55 AM, Juergen Sauermann <juergen.sauerm...@t-online.de> wrote: Hi Blake, It was disabled because otherwise - as you have noticed - it would crash. The reason is that )LOAD (but also )SIC and )CLEAR) clears the SI while it is  still in use for returning the result of ⍎ and other things. There is no clean way to do this. You might consider )COPY instead of )LOAD because )LOAD would also kill the function that executes the ⍎')LOAD ws' /// Jürgen On 11/14/2014 11:00 PM, Blake McBride wrote: Greetings, I see the last update disabled execute of )LOAD.  (I also noticed the prior version corrupted memory on it.)   IMO, getting this working would be real helpful.  Sometime I have a really large workspace.  I can split it up into several workspaces and execute a )LOAD to get to the desired functionality.  Also, with execute )LOAD I can have a startup workspace that provides a menu of applications.  When the user selects which application they want I can execute a )LOAD. It would really be valuable to get this working. Thanks. Blake