Re: Problem with rev 1217
- Posted by mattlewis (admin) Oct 28, 2008
- 993 views
I can run IDE104 and stand-alone editor with rev 1220 and can translate, compile the stand-alone Editor.exw. I tried EuWinGui and there is also no problem. With some changes of the keywords entry and label, running the arwen library and translating / compiling the demos work too. (Edita seems not to be available any more)
But translating IDE does still not work. There are error messages e.g:
Ok, I hadn't tried that. I'll look at the translator next.
My personel impression is that starting the splash screen of interpreted IDE needs more time with rev 1220 than with rev 1216.
This is probably true. The reason is that the IDE declares some globals in certain files, and then other files use those globals without ever including the file where the globals are defined. This causes extra overhead in the parsing. There were recent changes to how this worked, since unincluded globals could mask forward referenced included symbols.
CK found this problem when he had some code that used the old sort, and some that used the new sort. Basically, sequence.e and sort.e (I think it's those two) include each other, and use routines from each other, which is one big benefit of the new forward reference feature. Adding a few strategic include statements would speed up the parse time.
If eu.ex shows an error then should exw(c).exe not show this error too?
Not necessarily. They share the front end, but the back end of eu.ex is written in euphoria. So if the bug is in the euphoria backend, the error wouldn't be seen when you use the C backend. Although a C backend error in something like puts(), which is called by the euphoria based backend could show up. But a lot of the C interface is written in the euphoria back end, which appears to be what you've run into, so the bug is likely only in eu.ex.
Matt
