Sujet : Re: neos Universal Compiler and FORTRAN IV
De : rjh (at) *nospam* cpax.org.uk (Richard Heathfield)
Groupes : comp.theoryDate : 30. Mar 2025, 10:39:20
Autres entêtes
Organisation : Fix this later
Message-ID : <vsb3g8$digq$1@dont-email.me>
References : 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17
User-Agent : Mozilla Thunderbird
On 30/03/2025 09:57, Mikko wrote:
On 2025-03-29 10:11:13 +0000, Richard Heathfield said:
On 29/03/2025 09:51, Mikko wrote:
On 2025-03-28 14:14:10 +0000, Mr Flibble said:
>
<snip>
>
If a native FORTRAN IV compiler can parse it then neos can parse it as long as it is somehow expressable in the neos
attribute grammar.
>
If you don't know how to express it in the neos attribute
grammar then nobody knows and neos is not universal, at lieast
in the practical sense.
>
You don't understand, Mikko. You probably think that "neos can parse it" means that neos can parse it. What it really means is that /in Mr Flibble's head/ neos can parse it, and anything in Mr Flibble's head is right by definition, and /therefore/ neos can parse FORTRAN IV even if it can't.
I can understand that but that is not interesting. But the question whether it is easier to use neos as universal compiler than a web browser is interesting. A web browser
certainly can compile any programming language that can be
compiled if it is given a script (HTML+javascript) that
defines the source and target languages.
Yes, but does it halt?
-- Richard HeathfieldEmail: rjh at cpax dot org dot uk"Usenet is a strange place" - dmr 29 July 1999Sig line 4 vacant - apply within
Re: neos Universal Compiler
Re: neos Universal Compiler