Re: boot strapping euphoria idea
- Posted by jimcbrown (admin) Feb 12, 2015
- 1971 views
This is an idea that I have had for sometime but I don't have enough
knowledge of euphoria's internal design.
It is a fact that the translator can translate euphoria code to "C" code.
Now suppose that a user creates an standard include library of eu code that
will add a new feature to Eurphoria.
This feature could be tested fully in euphoria code, removing all the bugs.
Next the new standard library would be run through a new version of the translator.
The translator output would be a "C" plug-in module that would interface into
"C" code version of source which will be run through Watcom or some other supported compiler.
This would have created a new version of Euphoria sort of like boot strapping.
The advantage of this is that it would make it easier on the developers.
Any user could then submit a standard library for consideration for addition to Euphoria.
Please be gentle on the criticism of this idea.
We don't support Watcom any longer.
The general idea is sound, but the translator produces code that tends to be very hard to read. Building to a shared library and coming up with a standard oe plugin interface would probably be the easiest way to go. (You'd then come up with the odd situation of having the C runtime library implement a feature via a plugin written in Euphoria - and the plugin itself would depend on an older version of the C runtime library to implement that feature.)
