Re: EuCOM and Interpreter Bugginess
Elliott S. de Andrade wrote:
>
> 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.
That's really odd. I've never had a problem like this...What are you
running (machine/OS)?
> PS. Matt, you really should add "without warning" when you release EuCOM.
Yes, I usually put that into things, so this was likely a little
oversight.
> PPS. Matt, I didn't know you were an actor in disguise:
> <a
> href="http://www.imdb.com/name/nm0507535/">http://www.imdb.com/name/nm0507535/</a>
Oh, well, you found me. :P
Matt Lewis
|
Not Categorized, Please Help
|
|
