Regarding locked functions: I believe these came about at a time when
vendors sold not only computer time, but also software services. No doubt
this was used to hide details of a "proprietary" function from paying
customers...
On Wed, Jul 9, 2014 at 7:06 AM, Elias Mårtenson wrote:
> I can't say
Thank you. Confirmed working.
With this change, I believe that the component function library conforms to
the ISO spec.
https://github.com/TieDyedDevil/iso-apl-cf
On Wed, Jul 9, 2014 at 6:11 AM, Juergen Sauermann <
juergen.sauerm...@t-online.de> wrote:
> Hi David,
>
> thanks, I have changed t
I can't say it makes much sense in non-opensource programs either. My guess
is that these things are more of a relic of a time when people were
experimenting with such things. There is a reason no other languages do
this.
However, I do see a different use for "non-suspendible functions". I see it
Hi David,
thanks, I have changed the code so that all user-defined functions with
the cannot be suspended" attribute at the top of the )SI stack are pop'ed
before a new immediate execution context is pushed onto )SI. SVN 369.
I hope this is what the standard wants - the information about these
c
The ISO spec for the component file interface says: "The functions
described here must be written so that they do not suspend. Any errors
encountered or detected must be passed to the context from which the
function was invoked."
I believe that means that the function's "cannot be suspended" attri
