XPost: comp.theory   
   From: 643-408-1753@kylheku.com   
      
   On 2025-11-27, olcott wrote:   
   > On 11/27/2025 1:06 AM, Kaz Kylheku wrote:   
   >> You will never be taken seriously if you use languages that are   
   >> completely out of favor in CS academia for doing research in this kind   
   >> of topic.   
   >>   
   >   
   > It is only by making every slight nuance of the   
      
   You wouldn't recognize a slight nuance if it blew your leg off   
   with a 12 gauge. :)   
      
   > halting problem concrete thus never abstracting   
   > away key details that its error can be directly seen.   
   >   
   > A C interpreter version is my next level.   
      
   It's completely counterproductive to use a language that is full of   
   undefined behaviors, and fundamentally imperative, for this kind of   
   research. It is an immediate red flag for a crank.   
      
   You need extra validation to produce a convincing argument that   
   the C is correct, and that everything is purely functional.   
      
   Using C is a regression compared to the 1973 Incomputability paper from   
   Tony Hoare.   
      
    "In this paper we draw on the programming   
    language LISP.[7] for writing most of the   
    example programs. We have chosen this   
    language for the following reasons: 1) it is   
    fairly widely known, 2) it is a small and   
    simple language, 3) it is easy to represent   
    Lisp programs as data (S-expressions) which   
    can then be manipulated, 4) it is relatively   
    easy to write an interpreter of the language   
    in Lisp itself, and 5) it might initially seem   
    to be easy to write a program which tells   
    whether another program will terminate or   
    not."   
      
   Hoare (unsurprisingly) had better ideas than you, in 1973.   
      
   Regarding it beng easy to write a Lisp interpreter in Lisp;   
   in fact, John MacCarthy wrote the semantics of Lisp in Lisp,   
   on paper, before there was a Lisp interpreter!   
      
   Famously, Steve Russel took this specification and hand-translated every   
   Lisp expression to machine code (with calls to the necessary subroutines   
   for funtionsl like CONS, CAR, ATOM and whatnot). The result was a   
   working Lisp interpreter.   
      
   Supposedly MacCarthy was at first taken aback, insisting that Steve is   
   doing something wrong; that the specification is only intended as   
   a reference, not to be directly turned to executable code.   
      
   --   
   TXR Programming Language: http://nongnu.org/txr   
   Cygnal: Cygwin Native Application Library: http://kylheku.com/cygnal   
   Mastodon: @Kazinator@mstdn.ca   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)   
|