From: no.email@nospam.invalid   
      
   dxf  writes:   
   > Has it paid off - by which I mean completed apps that out of the blue   
   > access invalid memory?   
      
   It could be that catching more of those errors during development means   
   fewer make it out to deployment.   
      
   > 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.   
      
   The programs with the memory errors are likely more complicated than   
   typical Forth programs, deal with more maliciously crafted inputs, and   
   make heavier use of dynamic memory allocation than small embedded   
   programs are likely to.  My own Forth experience is even more limited,   
   but in it, I haven't even used arrays very much, especially for   
   user-supplied data.   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)