Path: ...!eternal-september.org!feeder3.eternal-september.org!news.eternal-september.org!eternal-september.org!.POSTED!not-for-mail
From: Tim Rentsch <tr.17687@z991.linuxsc.com>
Newsgroups: comp.lang.c
Subject: Re: Python recompile
Date: Wed, 19 Mar 2025 00:14:59 -0700
Organization: A noiseless patient Spider
Lines: 35
Message-ID: <86v7s5pk3w.fsf@linuxsc.com>
References: <vq1qas$j22$1@gallifrey.nk.ca> <vq4m0u$1ctpn$1@dont-email.me> <vq4n05$1d5dv$1@dont-email.me> <vq4om7$1dbo2$2@dont-email.me> <vq6dqh$1pskk$1@dont-email.me> <vq6f8p$1pmnk$1@dont-email.me> <vq6gqc$1qcp8$1@dont-email.me> <vq6ips$1pmnk$2@dont-email.me> <vq6j5h$1qosf$1@dont-email.me> <20250304092827.708@kylheku.com> <vq7g1p$1vmg5$1@dont-email.me> <vq8544$23f55$4@dont-email.me> <vq88s7$242vk$1@dont-email.me> <vq8cdq$24hi9$2@dont-email.me> <vq9di0$2db82$1@dont-email.me> <86frjruk1m.fsf@linuxsc.com> <vqaqnr$2l1ar$3@dont-email.me> <86bjudvnno.fsf@linuxsc.com> <vqdcko$36d74$1@dont-email.me> <86o6y4sinc.fsf@linuxsc.com> <vr3oc6$3di63$1@dont-email.me>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Injection-Date: Wed, 19 Mar 2025 08:15:00 +0100 (CET)
Injection-Info: dont-email.me; posting-host="f38801bdea7b04066d3e2a5989bc7bcf";
	logging-data="294776"; mail-complaints-to="abuse@eternal-september.org";	posting-account="U2FsdGVkX1/onpIvWurOH2xTegJmXMWyP9oidmVvY90="
User-Agent: Gnus/5.11 (Gnus v5.11) Emacs/22.4 (gnu/linux)
Cancel-Lock: sha1:Wp0iXo1nfcSVk5sm/Lu/WcQUYgc=
	sha1:hUl4s5MTMrlUk7rnoz68qT1qDds=
Bytes: 2956

bart <bc@freeuk.com> writes:

> On 13/03/2025 21:52, Tim Rentsch wrote:
>
>> bart <bc@freeuk.com> writes:
>>
>>> Here however is a summary of these fictional tools:
>>>
>>> https://github.com/sal55/langs/blob/master/CompilerSuite.md
>>
>> I'm not interested in the tools.  What I am asking to see is
>> the language.
>
> I'm working on a document that summaries the features.

I expect some people will find it interesting reading.  It is
almost certainly worth writing, assuming there is an interested
audience.

My interest is seeing a definition of the language, including
at least a complete syntax, and some sort of description of
the semantics for each construct, especially those that look
or behave differently than familiar constructs in mainstream
languages.  Being concise or terse is okay;  I don't need to
read a belabored explanation of, for example, how function
calls work, if they work the same way that function calls in
C work.  But it is important, in this example, to say that
function arguments are always evaluated left-to-right (if
indeed that is the case), because it may change the meaning
of a code fragment relative to common expectations.

In short, I would like to see a minimal document that lets
me say with confidence that I can write code in the language
and that I can read any legal program in the language and
know what it does.