Re: Processor Speed is Biggest Factor in exw Program Opening
Matt Lewis wrote:
>
> Al Getz wrote:
> >
> > Well, it 'might' help to write the front end in C too.
> > I dont know how much this would help though, as the older
> > 2.4 version did not use iL code so it didnt have to generate
> > that too.
> >
>
> Incorrect. IL code has always been a part of euphoria. The difference
> is that before 2.5, euphoria executed any top level code that it encountered
> as soon as it was parsed. Which was why forward references using
> routine_id were impossible.
>
> We've traded away a bit of speed in the opening of large programs for a
> much more flexible, easily maintained and extended front end. I don't
> see any going back. I guess it's too bad for people who still have older,
> slower machines, but I think it's the right direction for euphoria.
>
> Matt
Hi Matt,
I didnt realize 2.4 generated iL code too, but it really doesnt matter
that much. The speed is the main issue, but thanks to the open source
and free .exe Euphoria the impact is a little less now, as anyone can
bind an executable (thanks to Rob for that) and make the program open
faster.
I dont see any going 'back' either, at least not to going back to
running before all the code is parsed, but it might help to do a
C front end, if anyone is inclinded to dig into this task 
At one time i thought i would be able to do this, but time seems
to have become a bigger factor lately.
I guess i could continue to do what i have done in the past for
programs that i really want fast. That is, build a windows dll for
the tasks that must be very very fast and use Eu for the base program.
This works out very well, especially since WATCOM is free too.
Take care,
Al
E boa sorte com sua programacao Euphoria!
My bumper sticker: "I brake for LED's"
From "Black Knight":
"I can live with losing the good fight,
but i can not live without fighting it".
"Well on second thought, maybe not."
|
Not Categorized, Please Help
|
|
