1. Hacking Euphoria
- Posted by SDPringle May 19, 2014
- 1312 views
Forked from My frustration
Long ago, I started writing a guide for how to add a builtin to EUPHORIA. I abandoned before finishing though. My idea was to provide run-time type information to EUPHORIA but decided to stop at name_of() which is part of the alternative literals branch. The guide is unfinished but could be finished given the right encouragement.
What do you want such a thing to do? You probably don't need it to be a builtin.
SDPringle
My frustration is that is no documentation to explain in detail how to add one function WRITTEN in Euphoria with one parameter ( a sequence ) that returns an ATOM.
I have been told that all I have to do is pass the routine_id is to look at the way coverage in version 4.1. Well that may be easy if you are a developer that understands everything about the details of using coverage but it is hopeless.
The user needs to know where to put the function written in euphoria.
Where is the callback is initially executed in the backend .
Someone has to write a DETAILED how to ADD a euphoria function to the interpreter
showing how to pass its routine_id from the backend to the frontend;
It must show ever file and place that needs code.
Don't say write the function in 'C' !
I had the idea that you could use the translator to translate a euphoria function to 'C'
and just place the translated function and compile into the interpreter.
But as you know the 'C' output from the translator splits across many files and uses
numbers for variables and etc.
2. Re: Hacking Euphoria
- Posted by jimcbrown (admin) May 19, 2014
- 1318 views
Forked from My frustration
Long ago, I started writing a guide for how to add a builtin to EUPHORIA. I abandoned before finishing though. My idea was to provide run-time type information to EUPHORIA but decided to stop at name_of() which is part of the alternative literals branch. The guide is unfinished but could be finished given the right encouragement.
I think such a guide would be extremely helpful and useful. You can certainly consider yourself to have my encouragement to finish it.
What do you want such a thing to do? You probably don't need it to be a builtin.
In BRyan's case, it doesn't need to be builtin. The key point is to be able to call an Euphoria-coded routine from the backend (as the 4.1 coverage code today does). But it'd probably be easier to do it with machine_funcs, for example.
