EuCOM and Interpreter Bugginess
There's something very strange going on here. If I run EuCOM.ew (in a
program or by itself to test), there are some weird results when there are
missing include files. If unicode.ew is missing, it works correctly. Namely,
it prints out that it can't find unicode.ew and waits. If, however,
unicode.ew exists and variant.ew or comerr.ew do not, the interpreter does
not error out properly. Initially, it prints out the name and EUINC path,
but before it can print out what the error really is, another machine error
occurs. This prints out its own message, which would be alright, but then it
procedes to crash entirely, without writing an ex.err.
The strange thing is: a) there is no code between the include statements for
unicode.ew, variant.ew, and comerr.ew, b) there is no code executed in
unicode.ew that could cause this sort of problem (there are only function
links), and c) of course the fact that the interpreter decides to royally
crash too.
PS. Matt, you really should add "without warning" when you release EuCOM.
PPS. Matt, I didn't know you were an actor in disguise:
http://www.imdb.com/name/nm0507535/
|
Not Categorized, Please Help
|
|
