Sujet : Re: Is Scryer Prologs failure measurable? (Was: Holy Grail makes People Disappear)
De : janburse (at) *nospam* fastmail.fm (Mild Shock)
Groupes : comp.lang.prologDate : 10. Aug 2024, 13:19:53
Autres entêtes
Message-ID : <v97icn$11mpq$1@solani.org>
References : 1 2 3 4 5 6
User-Agent : Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:91.0) Gecko/20100101 Firefox/91.0 SeaMonkey/2.53.18.2
Hi,
A few days age we improved the cross referencer,
to deal with the many target platforms. The
old cross referencer for example showed:
xor/3 nova/Eval.java
nova/eval.mjs
nova/eval.py
Meaning the evaluable function xor/3 is
available in Java, JavaScript and Python.
What we now do, we simply show:
xor/3 nova/eval.*
Soon the wildcard will mean C# as well,
and not only Java, JavaScript and Python.
Extending the proof of concept for Prolog
compiler 100% written in Prolog itself.
Bye
Mild Shock schrieb:
Hi,
The C# backend was already planned 3
years ago. But then we gave priority to
a Python backend.
But Python is the worst language on this
planet. Their module approach doesn't
really have export modifiers.
Nevertheless they top TIOBE:
Highest Position (since 2001): #1 in Aug 2024
https://www.tiobe.com/tiobe-index/python/
Superficially even Prolog has a better
module system, although export restrictions
are not enforced, you can pretend to do exports,
via the module/2 directive. After we
completed the Python backend, we recently
did the Java backend. But this was not
only done for the benefit of Java, but
also as an intermediate step for the C#
backend. We are pretty close to that
everything has stabilized, and it would
be a good timing to do the C# backend then.
Bye
Mild Shock schrieb:
Hi,
>
Currently I wish to add a C# sharp backend,
and also show some Unity integration.
>
But I am facing some health problems, some
nasty virus infection, which still persists
>
a little bit. Either I will be able to do
it in 2024, or you wont here anything
>
from me anymore...
>
LoL
>
Bye