Re: Python recompile

On Sat, 15 Mar 2025 13:39:39 +0000
bart <bc@freeuk.com> gabbled:

On 15/03/2025 12:03, Muttley@dastardlyhq.com wrote:

It doesn't, that was kind of the point. win32 can't do fork().

>
So, WTF does that have to do with the subject? I can also ask how what

Umm, you're trying to promote your language. Might be helpful if it did
something fucking useful. Or is it just a toy?

You do realise its utterly trivial to create a script or even an alias under
*nix that will compile and run in one go. You declaration that being able to
do both with one command is some kind of quantum leap in functionality is
laughable.

>
OK. Try it with CPython: start with no CPython executable, just the source files. You want to be able to run hello.py with one command that will build CPython from source and run it.

Something like this I imagine:
alias hello="cd cpython;make;bin/python hello.py"

Tell me how long it took to write the script, how long it took to run,

10 secs and no idea. How long does it take to build your language from scratch?

My example didn't need a script; it ran in 0.1 seconds, and generated zero files. It needed one tool, the compiler.

So what language is your compiler written in? Does it magically just work or
does it have to be built first?

Yes it is a 'quantum' leap compared with how things are usually done.

How exactly?

if you want an inefficient build. Most people however don't like rebuilding
from scratch everytime there's a code change in a single module, hence makefiles.

>
Here, you don't seem to understand what this is about.

I understand that everytime I ask you something relevant your answer is
the equivalent of "Look! Squirrel!"