Yes. It seems the APL2 example code is not very good. If an error occurs,
you really don't want to just continue running. :-)

Regards,
Elias


On 5 August 2014 18:23, Juergen Sauermann <juergen.sauerm...@t-online.de>
wrote:

>  Hi Elias,
>
> it was available ,but behaves differently. ⎕ES stops execution
> while the ERR function only displays an error if it occurs.
>
> /// Jürgen
>
>
>
>
> On 08/05/2014 06:42 AM, Elias Mårtenson wrote:
>
> Thank you. I see now how it works. Personally, I'd use Quad-ES to set an
> error state instead. Was Quad-ES available on APL2?
>
>  Regards,
> Elias
>
>
> On 5 August 2014 01:42, Juergen Sauermann <juergen.sauerm...@t-online.de>
> wrote:
>
>>  Hi Elias,
>>
>> ERR is indeed a function, defined on page 49 of that document.
>>
>> /// Jürgen
>>
>>
>>
>> On 08/04/2014 08:13 AM, Elias Mårtenson wrote:
>>
>> I was browsing the APL2 documentation, and came across the following code
>> (page 56, on the PDF here
>> <http://publibfp.boulder.ibm.com/epubs/pdf/h2110720.pdf>):
>>
>>  [0]  Z←NAME GETW N
>> [1] ⍝ GET ITEMS N FROM THE TABLE NAMED NAME
>> [2]  Z←''
>> [3]  →('NOT A VALID TABLE NAME' *ERR*~(⊂NAME)∊TABLES)/0
>> [4]  TAB←⍎NAME
>> [5]  B←N∊TAB[;1]
>> [6]  →0ρ('ITEM(S)'((~B)/N)'NOT FOUND')*ERR*~^/B
>> [7]  →(~∨/B)/0  ⍝ EXIT IF NONE FOUND
>> [8]  Z←(TAB[;1]∊N)⌿›TAB
>>
>>  What is ERR here?  It seems like a function that sets some error state?
>> It certainly looks like something useful to have. I can't think of any way
>> I could build this myself though.
>>
>>  Regards,
>> Elias
>>
>>
>>
>
>

Reply via email to