Re: Why some ...+ FASTER PARSING than 2.4 !
Al Getz wrote:
> Juergen Luethje wrote:
>>
>> Robert Craig wrote:
>>
>> <snip>
>>
>>> However, Euphoria is supposed to be a simple language.
>>> I would not want to add this complexity to the front end,
>>> plus complexity to the manual, as well as having newbies
>>> constantly say "what are those extra files for?".
>>> In theory it would be "transparent", but people would still
>>> see the extra files lying around, and if anything went wrong,
>>> they would wonder if they were really up-to-date.
>>>
>>> At some point, I'm going to look into shrouding of include
>>> files, to get a .il that can be included. I'm not sure how
>>> it will go, but I'd rather do that than complicate the
>>> whole process of running the interpreter. I do not want to
>>> introduce another type of intermediate file.
>>
>> I think this is actually the way to go! I hope it will be possible
>> to create .il files that can be included (or linked or whatever).
>> Very much appreciated!
>>
>> <snip>
>>
>
> Hi Juergen and Rob,
>
> Some interesting ideas here.
The idea -- and the desire -- to include .il files came up shortly after
Eu 2.5 was released. 
> I can start to see something like:
>
> without parse (perhaps in il code)
>
> at the beginning of a file to tell the Eu interpreter not to parse
> the file, that it's an il file so it doesnt need it.
> If there was enough info stored in the il file the Eu inter. could just
> add it to the collection instead of having to first parse it.
Using Eu 2.4, it is possible to include pre-parsed (shrouded) files
without the need of a special "with" clause. This is simple and
straightforward. I don't see an advantage when we would have to use such
a "with" clause.
> This would mean HUGE programs could parse actually FASTER than the
> old method (pre 2.5) (!!!!!) if they were built using several includes.
Yes, faster than the pre 2.5 method when plain source code text files
are included. However, at least with Eu 2.4 we also could/can include
pre-parsed (shrouded) files. I think not many people have done so,
though.
BTW: You can shroud include files (e.g. Win32lib) with Eu 2.4, and then
include these shrouded (= pre-parsed) files in your Eu 2.5 programs!!!
> The only include file we'd have to modify was the one we were
> working on (debugging) at the time, and we could always work it
> so that the untested code was in, yes, a different include file than
> the main program. Once debugged, stick it in with the rest by
> specifying that it's pre-parsed.
> I can see load times actually being FASTER than 2.4 was!
> This would be really GREAT!
>
> Heck, i wouldnt even mind
>
> include preparsed MyFile.ew (optional word: 'include')
I hope this will not be necessary. Euphoria should be smart enough to
detect itself, which files contain pre-parsed code.
> This way we'd have direct control over which files we want to debug
> and those already done and still have everything load super fast!
>
> If it turned out that we did have an error in a file that was
> included as 'preparsed' then we'd just have to go back and include
> the original file, but that's life...no big deal really.
Yep. Even Rob will probably not be able to create a DWIM
(Do-What-I-Mean / not what I write) interpreter or translator.
<snip>
Regards,
Juergen
--
Have you read a good program lately?
|
Not Categorized, Please Help
|
|
