1. exactly what do --use*-translator do?
- Posted by rkdavis Feb 12, 2013
- 1254 views
this is probably a question for matt or ira but as the borked builds (anything using console.e) build ok (but don't work) when using --use-binary-translator and freeze when building with --use-source-translator (default) could you explain the difference in words of 1 syllable as i'm being a bit dense atm.
[Ira, what exactly are you changing to build everything with -O3 ? I think i've missed a few places as some stuff seems to still be building as-O2 or no optimization]
2. Re: exactly what do --use*-translator do?
- Posted by jimcbrown (admin) Feb 12, 2013
- 1214 views
this is probably a question for matt or ira but as the borked builds (anything using console.e) build ok (but don't work) when using --use-binary-translator and freeze when building with --use-source-translator (default) could you explain the difference in words of 1 syllable as i'm being a bit dense atm.
Using the binary translator means it runs euc to build everything. Using the source translator means it runs "eui ec.ex" to build everything.
The difference? The binary translator runs your older copy of Euphoria (the "eubins") to do the translation, while the source translator runs the latest, freshest hg revision in your working copy - allowing you to take advantage of new features and changes right away. (The source translator bootstraps itself using eui from the eubins.) Using the binary translator is faster, but devs typically run with the source translator as that is better at revealing new bugs.
3. Re: exactly what do --use*-translator do?
- Posted by Jerome Feb 12, 2013
- 1218 views
[Ira, what exactly are you changing to build everything with -O3 ? I think i've missed a few places as some stuff seems to still be building as-O2 or no optimization]
Oops, I answered this in the original thread!
Using the binary translator means it runs euc to build everything. Using the source translator means it runs "eui ec.ex" to build everything.
The difference? The binary translator runs your older copy of Euphoria (the "eubins") to do the translation, while the source translator runs the latest, freshest hg revision in your working copy - allowing you to take advantage of new features and changes right away. (The source translator bootstraps itself using eui from the eubins.)
Just so I understand, both methods translate the same Euphoria source files into C, but using an older binary translator means your translated files might not contain all the new features in the Euphoria source files?
Thanks,
Ira
4. Re: exactly what do --use*-translator do?
- Posted by jimcbrown (admin) Feb 12, 2013
- 1176 views
Just so I understand, both methods translate the same Euphoria source files into C, but using an older binary translator means your translated files might not contain all the new features in the Euphoria source files?
Thanks,
Ira
Yes. Stuff in the stdlib would probably be unaffected (though not always), but things like new bug fixes or speedups might only appear with the source translator (or after you've retranslated the binary translator from source).
5. Re: exactly what do --use*-translator do?
- Posted by rkdavis Feb 12, 2013
- 1208 views
thanks, i think i understand it now and i'll make the changes you suggested in the other thread and see how consistantly i can build.
does 4.0.5 build/run ok on ARM? if yes then might be worth building a deb for the raspberry pi and announcing on the raspberry pi forums as IMHO i think euphoria makes a good starting/learning/doing stuff language & we can say "yah boo sucks" to the pythonistas :)
