OpenEuphoria

Re: Error

• Posted by David Cuny <dcuny at DSS.CA.GOV> Jun 08, 1998
• 649 views

Brigitte wrote:

>>D:\EUPHORIA\EIGENO~1\TEST1\TEST1.EXE:378
>>BM has not been declared
>>BM BN=20
>>   ^=20
>>What does it mean? And how can I resolve it?

Well, you obviously have an error in your program, and Euphoria is =
trying to show you where the problem is.=20
To see the error, look at line 378 in your TEST1.EX file.

You are seeing "weird" stuff because you are running an EXE file, not an =
EX program. An EXE file is a bound EX file.

When you BIND a program into an EXE, Euphoria "condenses" is down, =
converting all your nice your function and variable names into 2 byte =
codes such as "AD" and "QY". So when it tries to show you the error, you =
get something fairly unreadable. This is a good thing, because you =
typically don't want to distribute your EXE file and have people see =
your code. From a testing standpoint, however, this is a bad thing.

For testing purposes, it's easier to wait until the program is fully =
debugged before binding it, running it from the command line as:

   EX TEST1.EX

or the IDE (such as ED). Then, once you are sure you have the bugs out, =
and don't need to see the names of your functions and variables, you can =
bind the program.

Another option is to use the -FULL_KEYWORDS flag when binding your file, =
such as:

   BIND TEST1 -FULL_KEYWORDS

I *think* this will bind your program, and leave the functions and =
variables with their original names, so they will give useful error =
messages. Of course, it's much easier for someone to read the source =
code in your EXE if you do that.

-- David Cuny