OpenEuphoria

Re: Euphoria 2.5 alpha

• Posted by akusaya at gmx.net Nov 17, 2004
• 558 views

1.
R> Let me know of any bugs in 2.5, even if it's just documentation.
R> We'll do a beta release in a month or so.

If you say so, then,
in source/eu.ex
-- usage:
--        ex ex.ex prog.ex     -- run a Euphoria program for DOS
--        exw ex.ex prog.exw   -- run a Euphoria program for Windows
--        exu ex.ex prog.exu   -- run a Euphoria program for Linux/FreeBSD
Should be eu.ex instead of ex.ex, right?


2. Is it right? That the shortcuts in Start Menu refers to ec/ecw, not
ex/exw.

3. I'm still confused about .il files. How to produce (unshrouded) .il
files?

4.  How  can we use backend.exe ? For running .il files? Then where is
the  .il  files?  BTW, the size of backendw.exe is 64 KB, not too much
difference with 2.4 exw.exe (72 KB)

5.  How  about  removing  routines  of  position(), put_screen_char(),
clear_screen(), text_color(), etc, etc from backendw.exe and providing
the implementation at the include file, like this:

-- at graphics.e
global procedure text_color(color c)
    if platform() = DOS32 then
        machine_proc(M_SET_T_COLOR, c)
    elsif platform() = WIN32 then
        c_proc(WindowsAPIThatChangesTextColor, {...})
    elsif platform() = LINUX then
        c_proc(NcursesLibThatChangesTextColor, {...})
    end if
end procedure

So backendw.exe doesn't need to implement the
machine_proc(M_SET_T_COLOR, c), including it's error checking.

The reason is that win32 programming usually doesn't deal with
consoles.


6. Bug: 2.5 exw.exe doesn't close the source file after parsing
program, while 2.4 does. For example exw.exe program.exw. While
program.exw is running, file program.exw is still open!