home bbs files messages ]

Forums before death by AOL, social media and spammers... "We can't have nice things"

   comp.lang.forth      Forth programmers eat a lot of Bratwurst      117,927 messages   

[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]

   Message 117,586 of 117,927   
   albert@spenarnc.xs4all.nl to Anton Ertl   
   Re: 0 vs. translate-none   
   29 Sep 25 11:03:25   
   
   In article <2025Sep29.075402@mips.complang.tuwien.ac.at>,   
   Anton Ertl  wrote:   
   >albert@spenarnc.xs4all.nl writes:   
   >>In article <2025Sep25.083640@mips.complang.tuwien.ac.at>,   
   >>Anton Ertl  wrote:   
   >>>As a programmer, if you know how the systems you are interested in   
   >>>behave, you can make use of that knowledge; the program will then not   
   >>>conform to the current standard, but still work as intended on these   
   >>>systems.  In a standard based on common practice, that's the only   
   >>>way to achieve progress.   
   >>   
   >>That is for unsafe languages like Forth or Fortran. For Algol / Pascal   
   >>program' s behave the same for all systems, except for restrictions   
   >>due to the program environment like "memory exhausted" " too many   
   >>nesting levels", " floating point overflow" for the language model   
   >>is based on infinite resources.   
   >>The language definition is nailed down from day one and there is no   
   >>ambiguous holes to be filled.   
   >   
   >Nice fantasy.   
   >   
   >For Algol 60 (not sure about Algol 68), they could not even agree on a   
   >machine-readable representation of the programs.  I.e., you cannot   
   >write a file containing any Algol 60 program that is guaranteed to be   
   >compiled by all Algol 60 compilers; the behaviour of the program is   
   >only when you have compiled it and can run it.   
      
   The character set wherein the program is represented is irrelevant.   
   I cannot compile a EBCDIC FORTRAN program in my linux system.   
      
   For Algol 68 there was a small hole in the original report   
   specification that led to the "revised report".   
      
   >   
   >In Pascal, the program can access a pointer after DELETEing its   
   >contants, and you can also DELETE the pointer several times, all not   
   >defined by the language and typically resulting in programs behaving   
   >other than intended.  The same kinds of execution sequences are often   
   >mentioned as vulnerabilities in C programs (use after free, double   
   >free); this only is not reported widely for Pascal programs because   
   >there are no Pascal programs in wide use.   
      
   That was an oversight, not intended.   
      
   >   
   >- anton   
   --   
   The Chinese government is satisfied with its military superiority over USA.   
   The next 5 year plan has as primary goal to advance life expectancy   
   over 80 years, like Western Europe.   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)   

[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]


(c) 1994,  bbs@darkrealms.ca