From: dxforth@gmail.com   
      
   On 4/05/2025 2:02 am, Anton Ertl wrote:   
   > dxf  writes:   
   >> Checking the doc it says:   
   >>   
   >>  9.3.5 Possible actions on an ambiguous condition   
   >>   
   >>  A system choosing to execute THROW when detecting one of the ambiguous   
   >>  conditions listed in table 9.3.6 shall use the throw code listed there.   
   >   
   > Calling ABORT or QUIT is not an ambiguous condition, so that section   
   > plays no role there.   
      
   Yet ABORT ABORT" and QUIT are present in the table and assigned codes.   
   It is clear to me all three are candidates for CATCHing and that this   
   was the intent.  This is confirmed by the EXCEPTION EXT wordset in which   
   ABORT and ABORT" are required to be CATCHable irrespective of their   
   category.   
      
   >> So while CATCH and THROW are compulsory (EXCEPTION wordset), there is no   
   >> requirement to implement any of the codes listed in the table.  Only if   
   >> the EXCEPTION EXT wordset is implemented must the codes for ABORT and   
   >> ABORT" be used.  Thus a system may implement the following if it wishes:   
   >>   
   >>  : QUIT -56 THROW ;   
   >   
   > That would not be a standard system, because in a standard system QUIT   
   > must do what 6.1.2050 QUIT says, and "-56 THROW" is not a correct   
   > implementation of that.   
      
   No for the fact QUIT is CATCHable by virtue of its inclusion in the table   
   of codes in Section 9.  If OTOH you believe the inclusion of ABORT ABORT"   
   and QUIT was made in error then you have the option of testing that by   
   making a proposal to have them removed.   
      
   --- SoupGate-DOS v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)