Path: ...!eternal-september.org!feeder3.eternal-september.org!news.eternal-september.org!eternal-september.org!.POSTED!not-for-mail
From: Mikko <mikko.levanto@iki.fi>
Newsgroups: comp.theory
Subject: Re: neos Universal Compiler and FORTRAN IV
Date: Mon, 31 Mar 2025 11:28:49 +0300
Organization: -
Lines: 38
Message-ID: <vsdjo1$3qcfv$1@dont-email.me>
References: <UX6BP.512735$Kb9a.408485@fx16.ams4> <vr3ir8$39jtg$1@dont-email.me> <3KgBP.513160$Kb9a.94584@fx16.ams4> <vr6948$1jnlo$1@dont-email.me> <KWEBP.424367$NN2a.82900@fx15.ams4> <vr8pi1$3r8lv$1@dont-email.me> <NrYBP.191725$C8m7.108955@fx11.ams4> <vrbu8h$2km30$1@dont-email.me> <S7fCP.743699$nb1.627959@fx01.ams4> <vre64b$lcu3$1@dont-email.me> <2AACP.939386$gHk7.592478@fx17.ams4> <vreqb6$174ma$1@dont-email.me> <vs6334$2mosu$1@dont-email.me> <S8yFP.697907$B61.152494@fx02.ams4> <vs8frb$11o2g$1@dont-email.me> <vs8h01$12ie6$1@dont-email.me> <vsb11b$2m0ck$1@dont-email.me> <vsb3g8$digq$1@dont-email.me>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
Injection-Date: Mon, 31 Mar 2025 10:28:50 +0200 (CEST)
Injection-Info: dont-email.me; posting-host="9db5ebc22b0a66665dc12d47e37818b7";
	logging-data="4010495"; mail-complaints-to="abuse@eternal-september.org";	posting-account="U2FsdGVkX195UlxqyGtMWvMhBB6jBeF7"
User-Agent: Unison/2.2
Cancel-Lock: sha1:er1rn/Cd6nMIPrHtGa1aM79GHrA=
Bytes: 2870

On 2025-03-30 09:39:20 +0000, Richard Heathfield said:

> 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?

If it does not deliver the object file in reasonable time the script is bad.

-- 
Mikko