1. eecs bugs or euphoria bugs
------=_NextPart_000_0029_01BFF64D.7AE4E880
boundary="----=_NextPart_001_002A_01BFF64D.7AEE1040"
------=_NextPart_001_002A_01BFF64D.7AEE1040
charset="iso-8859-2"
Content-Transfer-Encoding: quoted-printable
first two bugs i think are bugs in euphoria interpreter:
=20
BUG # 1:
in EE:CS editor, when you try to run program that uses more complex =
graphics, like bump.ex (which i think is the best graphics demo in =
euphoria) picture is not like it should be. i think there is bug in =
system_exec command, where you define something about graphics with =
second parameter. i tried all three numbers, none seem to work.
BUG # 2: current_dir bug: inside editor you run program. if that program =
then tries to open file just by name, like fn=3Dopen("file.txt") which =
exists in it's current directory, it cant open it, but it should. this =
is because current_dir is the one where eecs runs and not where current =
program runs. current directory i think should be allways where current =
program is running, like in c. Every time when exw.exe or ex.exe is run, =
it should set current directory to directory where current program =
which is run is, and then possibly set it back.
i added two files. put them in different directory than eecs directory. =
try to run it outside (it will open it) and inside the eecs editor (it =
won't open).
another little bug: if you open file which has last line blank and with =
null length (just '\n' character), it is not read.
------=_NextPart_001_002A_01BFF64D.7AEE1040
charset="iso-8859-2"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META content=3D"text/html; charset=3Diso-8859-2" =
http-equiv=3DContent-Type>
<META content=3D"MSHTML 5.00.2614.3401" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT face=3DVerdana size=3D2>first two bugs i think are bugs in =
euphoria=20
interpreter:</FONT></DIV>
<DIV><FONT face=3DVerdana size=3D2></FONT> </DIV>
<DIV><FONT face=3DVerdana size=3D2>BUG # 1:</FONT></DIV>
<DIV><FONT face=3DVerdana size=3D2>in EE:CS editor, when you try to =
run program=20
that uses more complex graphics, like bump.ex (which i think is the best =
graphics demo in euphoria) picture is not like it should be. i =
think there=20
is bug in system_exec command, where you define something about graphics =
with=20
second parameter. i tried all three numbers, none seem to =
work.</FONT></DIV>
<DIV> </DIV>
<DIV><FONT face=3DVerdana size=3D2>BUG # 2: current_dir bug: inside =
editor you=20
run program. if that program then tries to open file just by name, like=20
fn=3Dopen("file.txt") which exists in it's current directory, it cant =
open it, but=20
it should. this is because current_dir is the one where eecs runs and =
not where=20
current program runs. current directory i think should be allways where =
current=20
program is running, like in c. Every time when exw.exe or ex.exe is run, =
it=20
should set current directory to directory where current =
program which=20
is run is, and then possibly set it back.</FONT></DIV>
<DIV><FONT face=3DVerdana size=3D2>i added two files. put them in =
different=20
directory than eecs directory. try to run it outside (it will open it) =
and=20
inside the eecs editor (it won't open).</FONT></DIV>
<DIV> </DIV>
<DIV><FONT face=3DVerdana size=3D2>
<DIV><FONT face=3DVerdana size=3D2>another little bug: if you open file =
which has=20
last line blank and with null length (just '\n' character), it is not=20
------=_NextPart_001_002A_01BFF64D.7AEE1040--
------=_NextPart_000_0029_01BFF64D.7AE4E880
name="file.txt"
2. Re: eecs bugs or euphoria bugs
Skoda writes:
> BUG # 1:
> in EE:CS editor, when you try to run program that uses more complex
> graphics, like bump.ex (which i think is the best graphics demo in
> euphoria) picture is not like it should be.
Mic is doing fancy non-standard graphics using special
machine code. It looks fine when run from ed (Esc e) or eecs
using my ATI graphics card.
> BUG #2:
> Every time when exw.exe or ex.exe is run, it should set current
> directory to directory where current program which is run is,
> and then possibly set it back.
No thanks. I think the application should worry about this.
You can use current_dir() and chdir() to achieve whatever you want.
current_dir() simply reports the system's idea of the current
directory. I don't want to play any games here.
> another little bug: if you open file which has last line blank
> and with null length (just '\n' character), it is not read.
I couldn't duplicate this with ed or eecs.
Regards,
Rob Craig
Rapid Deployment Software
http://www.RapidEuphoria.com
3. Re: eecs bugs or euphoria bugs
On Tue, 25 Jul 2000 15:32:02 +0200, =?iso-8859-2?B?qWtvZGE=?=
<tone.skoda at SIOL.NET> wrote:
>first two bugs i think are bugs in euphoria interpreter:
>
>BUG # 1:
>in EE:CS editor, when you try to run program that uses more complex
graphics, like bump.ex (which i think is the best graphics demo in
euphoria) picture is not like it should be. i think there is bug in
system_exec command, where you define something about graphics with second
parameter. i tried all three numbers, none seem to work.
I don't _think_ the problem is with EE:CS, but I never rule out the
possibility these days. How exactly are you using system_exec()? The help
file states clearly that that the command must be a valid executable (not
just any DOS command), and that system_exec() is a function, not a
procedure like system(), so it needs to be used like this:
integer errorlevel
errorlevel = system_exec("somecommand.exe /parameters", 2)
>BUG # 2: current_dir bug: inside editor you run program. if that program
then tries to open file just by name, like fn=open("file.txt") which exists
in it's current directory, it cant open it, but it should. this is because
current_dir is the one where eecs runs and not where current program runs.
This is a genuine bug, but thankfully it's not a serious one.
Use full pathnames if you find it really annoying.
The bugfix will probably consist of me adding "lfnchdir(currentDir)" before
the ex/exw system-call if-statement, so if you want to run off of the
source code rather than the compiled version, you could probably add the
fix yourself...
Sorry about the bug tho...
>another little bug: if you open file which has last line blank and with
null length (just '\n' character), it is not read.
Which mode does it happen in? I can't seem to recreate this bug even when I
create a 1 byte file containing a '\n'. It loads fine.
Carl
