Re: THROW codes and ambiguous conditions

On 6/2/25 10:23 PM, dxf wrote:

On 3/06/2025 5:20 am, Hans Bezemer wrote:

On 02-06-2025 12:44, albert@spenarnc.xs4all.nl wrote:

In article <nnd$5d07338c$61b87fbd@d4d89ef8da41e19e>,
Hans Bezemer  <the.beez.speaks@gmail.com> wrote:

On 31-05-2025 03:10, dxf wrote:

<SNIP>

not a "hard" code. I mean, even in their freshman years CS students are
taught to use enums and constants instead of literals.

>
That is constants that are used more than once with the same meaning.
It is a deadly sin to use throw codes more than once, so this doesn't
apply.

>
Hans Bezemer

>
Wrong. It's a way to abstract a numerical literal - so if things happen to change, you don't have to change them everywhere. It's also a way to self-document a program. Any idea what -22 THROW does (without consulting the standard)? Any idea what E.BADADR THROW does?

 In the early days of microcomputing memory was severely limited and error codes
were used to save space.  But how much need today and what's wrong with ABORT"?
I don't use forth for scripting which might require sending codes and can't think
of an app where I've used codes.  Is the ANS list of error codes aimed at special
needs?  Because FWIW I'm not feeling any.
 

Oh dear... brings up an amusing and, at the time, a tedious customer interaction...
I was leading a group of non-native English speaking programmers making Windows applications. And of course they tried to save space in the error string table.  One of the windows in the system was the 'Analysis Window'.
When the error came it proclaimed a fault in the user's Anal Wind.
Customer support loved that one.  My boss didn't.
-J