1. FW: Euphoria To C Translator - Beta-2
Another post that didn't make it the first time...
-----Original Message-----
From: Matthew Lewis
> -----Original Message-----
> From: Robert Craig [mailto:rds at RapidEuphoria.com]
> The size and speed of the code was improved slightly,
> and several bugs were removed. The last-minute
> bug reported on this list yesterday will be fixed
> in the next release.
I've noticed some strange things. For one, 'without trace' seems to have no
effect, and printf seems to bomb if the last argument is an atom. More
important, however, is that I've got a program that crashes like no other Eu
program I've ever written/translated.
The program's based on EuCOM and EuSQL. It runs beautifully interpreted
(bound or unbound). Translated, everything runs fine until I begin filling
in cells (I'm using the same ActiveX control as in the demo), using
IDispatch::Invoke to call methods TextRC / NumberRC. Even though the calls
to Invoke return 0 (which indicates success), the translated code seems to
think the return value is an empty sequence. At least that's what '?
ok'-->'StdPrint(1, _ok, 1)' prints to the screen. These are not the first
calls to Invoke, BTW. Then it goes into my error reporting code, and the
return value is printed as zero.
After a few calls (sometimes on the first one, sometimes after 10 calls) my
computer completely locks up (sometimes I get an exception that pops up,
sometimes the blue screen of death, sometimes nothing). After I've
rebooted, ctrace.out and another debug file that I've been writing to are
completely empty--which they weren't before the crash.
I'm not quite ready to throw my hands up and send stuff to Rob, but I'm
getting close. ;) Has anyone else had strange experiences like this?
Matt Lewis
