Re: v2.5 Opens exw files wayyyy too slow
- Posted by Al Getz <Xaxo at aol.com> Dec 21, 2004
- 587 views
Hello again, Thanks for all the input from everyone here in the forum. I have to agree with some of the other posts, especially that one of the 'selling' points of Euphoria is that you can create what may be called "text file exe files" (text files that run as executables) but with a long delay before they open this changes everything. If the delay starts to get near the compile time for a C program we dont gain anything there. I couldnt live with 1.5 seconds to open an exw file, and i dont want to put out some $500 USD just to open exw files fast so the only use for v2.5 would be to bindw AFTER programs were written with v2.4 and tested under v2.4 . This means i wouldnt be able to use the new '$' or 'crash_routine()' because v2.4 doesnt recognize them, which brings me to my next question about the cost to upgrade from v2.4 to v2.5 . I would have preferred to see two versions, one that sequenced code as is, and one that sequenced code the old (2.4) way. It would be nice to debug with the old way, then bind with the new way. I could probably live with 0.25 seconds delay, 0.50 seconds would be getting a bit too slow. With v2.4 almost every program i have opens so fast you cant even notice it took longer than an exe file! This includes programs that use COM too. I think the longest to-open exw program i use frequently is a dictionary program, which does a lot of loading before it can run. The opening speed approaches 0.5 seconds under v2.4 . Take care, Al And, good luck with your Euphoria programming! My bumper sticker: "I brake for LED's"