From: cross@spitfire.i.gajendra.net   
      
   In article <10f35re$1q4rf$1@dont-email.me>,   
   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?   
      
   Almost nothing about Macro is memory safe; almost everything is   
   memory unsafe.   
      
   Memory safety in this context has a definition (albeit a kind of   
   loose one) and nothing about Macro aligns with that definition.   
      
   >You do realize that the lion's share of VMS is Macro???   
      
   I don't see how that's relevant, though it _is_ a testament to   
   the skill and professionalism of its authors that VMS works so   
   well despite the inherent dangers of Macro as the implementation   
   language.   
      
   	- Dan C.   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)