Error trapping with Dyalog APL: Difference between revisions
Jump to navigation
Jump to search
Error trapping with Dyalog APL (view source)
Revision as of 16:17, 4 November 2019
, 16:17, 4 November 2019→⎕SIGNAL
Miraheze>Adám Brudzewsky (Created page with "To write bug-free code in a complex system and to forecast all errors is impossible. Therefore, implementing some kind of error trapping in an application which is supposed to...") |
Miraheze>Adám Brudzewsky |
||
| Line 141: | Line 141: | ||
The best idea, however, is to use <source lang=apl inline>⎕NEXISTS</source> to check the file for already being created. In general it is a good idea to use error trapping only for extraordinary problems. | The best idea, however, is to use <source lang=apl inline>⎕NEXISTS</source> to check the file for already being created. In general it is a good idea to use error trapping only for extraordinary problems. | ||
=== <source lang=apl inline>⎕SIGNAL</source> === | === The <source lang=apl inline>⎕SIGNAL</source> system function === | ||
Note that an event which is <source lang=apl inline>⎕SIGNAL</source>led can be intercepted with <source lang=apl inline>⎕TRAP</source> but not <source lang=apl inline>:Trap</source> | Note that an event which is <source lang=apl inline>⎕SIGNAL</source>led can be intercepted with <source lang=apl inline>⎕TRAP</source> but not <source lang=apl inline>:Trap</source> | ||