From: clf@8th-dev.com   
      
   On 04/03/2024 3:10, dxf wrote:   
   > On 3/03/2024 4:54 pm, Ron AARON wrote:   
   >> One of the criteria for 8th was security -- among other things, making it   
   very difficult to do unsafe memory operations.   
   >   
   > Has it paid off - by which I mean completed apps that out of the blue access   
   > invalid memory?  I'm curious as to what exactly is behind the high rate of   
   > 'memory errors' that govt et al is reporting because in my limited experience   
   > programming in Forth, I'm just not seeing any.  I wonder if it has something   
   > to do with the practices employed in those other languages - such as the use   
   > of third-party libraries which programmers use essentially on faith.   
      
   That's a good question, for which I don't have an answer nor even any   
   metrics on which to base one.   
      
   While I, personally, rarely write code that has those sorts of issues   
   (at least, not in 30 years), I have worked in places where they were   
   fairly common. It depends a lot on the expertise and attention to detail   
   of the programmers, I think.   
      
   Since 8th is intended for "application programmers" who may have little   
   experience, and since one of its primary goals is "security", I've made   
   it difficult to smash memory -- whether on purpose or accidentally. Of   
   course, that makes it stray considerably from standard Forths.   
      
   TL;DR: I don't really know.   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)