Re: IL examples
- Posted by Robert Craig <rds at RapidEuphoria.com> Nov 26, 2004
- 580 views
Igor Kachan wrote: > I thought it would be nice to have in the main Euphoria > package some ready Euphoria IL programs as examples of > what is the new IL paradigm really. > > Say, both translators E-2-C or one of them. > Then you could make the registered translators compiled. At first I was going to include the PD translators in .il form, and make the registered translators as .exe, just as you suggest. However one of my goals with this release was to reduce the number of different executables and .zip files that I have to produce for a new release. Every component, PD or registered, has to be tested on every platform before release, and there were getting to be too many components. That's why I got rid of PD vs Complete Translator, and PD vs Complete Interpreter, and why I bundled all the Translator .zips into the one Interpreter .zip. I also found, when translating something like Judith's IDE that I appreciated the extra speed from a translated/compiled translator. > Now backend*.exes just hang up in the air and no one can > see what is an .il file. That's true. Though there's not much to see in a .il. Just a bunch of random characters all over your screen. I thought about just giving backend*.exe to those who register and letting them distribute it along with their apps, but it's better for the community if everyone has it automatically. Regards, Rob Craig Rapid Deployment Software http://www.RapidEuphoria.com