Re: Euphoria Compilers Available Soon
>My turn to be a critic...
>
> >That's another issue.
> >Robert *should* speed up interpretted Euphoria.
> >I see a million ways of doing it myself.
>
>So you have the source code of the Euphoria interpretter? Did you reverse
>engineer the interpretter? How else can you 'see' a million ways of
>speeding it up?
no I don't,but I do have common sense.
Here's one speedup.
Save the proclaimed "internal structure" of a Euphoria program to disk using
write(),then bind *that* with ex.exe.
Now all it's got to do is call read() one time and the porgram is loaded.
parsing the source every time you click on ex.exe is slow.
> >Hell, U4IA++ started out as a faster Euphoria interpretter.
>
>Hell, why not share your faster interpretter? Or did you not save your
>code from that stage of your project?
Didn't I just say "U4IA++ started out as a faster Euphoria interpretter"?
I think it's obvious from that line the U4IA++ used "to be" the
interpretter, since "it started out as" an interpretter.
Why do I have to repeat myself?
>I think I might have to put my hip waders on, it seems to be getting
>deeper...
>
>-- Brian
Do as you please,don't come crying at me when the rest of the world is
creating Playstation II games in U4IA++ while you are still trying to get
them GPF's out of your C source.
______________________________________________________
Get Your Private, Free Email at http://www.hotmail.com
|
Not Categorized, Please Help
|
|
