OpenEuphoria

Re: Euphoria 2.5 alpha

• Posted by Robert Craig <rds at RapidEuphoria.com> Nov 17, 2004
• 538 views

Akusaya wrote:
> 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?

Right. It's correct in source.doc
 
> 2. Is it right? That the shortcuts in Start Menu refers to ec/ecw, not
> ex/exw.

No, I made a last-minute typo in the INNO script.
I'm not sure how useful these shortcuts are anyway.
 
> 3. I'm still confused about .il files. How to produce (unshrouded) .il
> files?

The binder/shrouder will produce shrouded .il files
that can be read by backend.exe etc.
There is no way to produce an unshrouded .il file.
 
> 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)

backend.exe etc are there so you can run .il files
created by RDS or registered users of the Binder.
In 2.5, exw.exe is 103K. exw can now be enlarged in various ways
without necessarily enlarging backendw.exe.
 
> 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.

That code is pretty small. I wouldn't worry about it. 
 
> 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!

2.4 and earlier read the source in chunks. They closed the main source
file after reading the last chunk. This let you do things
like edit ed.ex using itself. I'll look into closing the
source after the front-end has completed. I guess it closes now
after execution. That will make 2.5 even better than 2.4 or earlier, 
in this respect (though how many people want to modify the
very source file they are currently running?)

Regards,
   Rob Craig
   Rapid Deployment Software
   http://www.RapidEuphoria.com