From: Danny@hyperspace.vogon.gov   
      
   Lawrence D'Oliveiro wrote:   
   > On Wed, 16 Oct 2024 20:57:17 -0500, Gary Scott wrote:   
   >   
   >> On 10/16/2024 7:51 PM, Lawrence D'Oliveiro wrote:   
   >>   
   >>> It’s annoying to find that if you try to DEALLOCATE an ALLOCATABLE   
   >>> variable that has not been ALLOCATEd (or that has already been   
   >>> DEALLOCATEd), this is an error.   
   >>>   
   >> The way these things are handled in Fortran is to add a "stat="   
   >> specifier.   
   >   
   > But I don’t want to catch errors as a result of invalid, non-NULL pointers   
   > -- let that be trapped as a runtime error as usual. I just want a free of   
   > NULL to be a harmless no-op.   
   >   
   > The trouble with “stat=” is like “ON ERROR GOTO” in BASIC of old: you   
   > either catch everything or nothing, you cannot be selective in the   
   > exceptions you catch.   
   >   
      
   Doesn't the content of STAT tell you what the error was?   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)