In article <2025Sep25.083640@mips.complang.tuwien.ac.at>,   
   Anton Ertl  wrote:   
   >dxf  writes:   
   >>"ambiguous condition:   
   >>A circumstance for which this Standard does not prescribe a specific behavior   
   >>for Forth systems and programs."   
   >>   
   >>"undefined" and "not prescribe a specific behavior" seem much alike to me.   
   >>Either way, the Standard is saying don't do this thing.   
   >   
   >Not really.  The standard just does not specify what happens in this   
   >case.   
   >   
   >>It's not as if   
   >>they'd said nothing about it and left it up to you.   
   >   
   >It's exactly that.   
   >   
   >As a programmer, if you know how the systems you are interested in   
   >behave, you can make use of that knowledge; the program will then not   
   >conform to the current standard, but still work as intended on these   
   >systems.  In a standard based on common practice, that's the only   
   >way to achieve progress.   
      
   That is for unsafe languages like Forth or Fortran. For Algol / Pascal   
   program' s behave the same for all systems, except for restrictions   
   due to the program environment like "memory exhausted" " too many   
   nesting levels", " floating point overflow" for the language model   
   is based on infinite resources.   
   The language definition is nailed down from day one and there is no   
   ambiguous holes to be filled.   
      
   Floating point is a slight exception. Programs can give   
   different answers due to precision.   
      
   >- anton   
   --   
   The Chinese government is satisfied with its military superiority over USA.   
   The next 5 year plan has as primary goal to advance life expectancy   
   over 80 years, like Western Europe.   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)