Re:
- Posted by Igor Kachan <kinz at peterlink.ru> Nov 10, 2001
- 1841 views
Hi sergio, ---------- > οΤ: sergio <sergelli at uol.com.br> > λΟΝΥ: EUforum <EUforum at topica.com> > τΕΝΑ: RE: > δΑΤΑ: Saturday, November 10, 2001 13:27 > Igor Kachan wrote: > > Imagine file.exe which you get with DJGPP, > > and DJGPP's **some** functions which are > > slower than same **some** functions of WATCOM, > > then file.exe you get with WATCOM will be > > faster, and ever ex.exe file.ex may be > > faster than that DJGPP's file.exe above. > > > > All these things about slower/faster > > require the very careful testing on > > monotask OS, for example in plain Dos-32 > > mode. > > > > Binded .exe, not compiled, may be 'more' > > fast than just ex.exe file.ex. > > > > Also these things are depending from the > > amount of free memory on your machine in > > the concrete session, and are random in > > the most cases. > > > > Try carefully another programs, not EU's, > > and you'll get same random results. > > > > I don't understand, if is fastest when uses EX.EXE > why someone uses an EXE file? > > thanks > Sergio, EU's EXE is faster for the most part, but sometimes under *some* conditions, you may get interpreted EU's program which is faster than compiled EXE EU's program, so just try and choose the fastest variant for yourself. You can use interpreted or binded or compiled with 6 different C compilers EU programs for any taste. Speed will be different for each case. Again, just try & choose the fastest variant for your concrete conditions (machine, OS, RAM, etc...). And remember, the *single wrong* operator in the concrete code (in any programming language) can decrease speed in 10..20 times sometimes. The speed depends on programmer's ability very very much. So, the special standard benchmark programs exist for the speed tests of the machines, languages, compilers, interpreters and so on. Regards, Igor Kachan kinz at peterlink.ru