Re: THROW codes and ambiguous conditions

On 2/06/2025 3:44 am, Hans Bezemer wrote:

 
Frankly - I find the standard severely lacking in this regard. They do provide a long table with "errors", but fail to properly define them. All we get is a description, open to interpretation. IMHO - this is not how to set up a standard.
 
If the condition is described in more detail elsewhere, a basic reference should be listed. Even better - a mnemonic should be attached, not a "hard" code. I mean, even in their freshman years CS students are taught to use enums and constants instead of literals.
 
But okay - as usual, we do what we can. But I'm *not* gonna include a huge list of non-contiguous messages. Forget it. I got thirty - and that's frankly enough.
 
3, 4, 5, 6, 9, 10, 12, 13, 19, 22 and 24 are "standard" as far as I'm concerned - and the rest is either missing ("dictionary overflow"? 4tH has no dictionary!) or located elsewhere.

I have 27 related to the compiler (more than I thought), 6 for turnkey/run-time and
7 for assembler if loaded, coded as ABORT"s or equiv.  These are listed/explained
in the doc.  iors (MS-DOS error codes mapped to -511..-257) are lefts for apps to
either THROW as decimal numbers or display as msgs.