From: arne@vajhoej.dk   
      
   On 11/12/2025 6:39 PM, Brian Schenkenberger wrote:   
   > On 2025-11-12 13:04:23 +0000, Dan Cross said:   
   >> I suspect that there is a lot of business code floating around   
   >> in memory-unsafe languages (MACRO-32, Pascal, maybe COBOL if   
   >> used in some odd ways) etc.  Not to mention FFI calls from safe   
   >> languages into unsafe code.   
   >   
   > What *exactly* is memory unsafe using Macro?   
      
   Just about everything.   
      
   :-)   
      
   But let us start with the definition of memory unsafe.   
      
   Wikipedia:   
      
   https://en.wikipedia.org/wiki/Memory_safety   
      
   My short version:   
   * no out of bounds check for array index   
   * allowing use of deallocated memory   
   * memory leak due to memory never being deallocated   
      
   Macro-32 does not take care of that - it leaves it all   
   to the developer.   
      
   Which would not be a problem if we had a million VAXMAN's,   
   but we don't, so it is a problem.   
      
   >                                  You do realize that the   
   > lion's share of VMS is Macro???   
      
   That code was written a long time ago.   
      
   Arne   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)