OpenEuphoria

Re: Bitten by a bug

• Posted by Robert Craig <rds at RapidEuphoria.com> Oct 20, 2005
• 530 views

Vincent wrote:
> I think if you do anything, it should be to make Borland 100% compatable with
> the Euphoria, like Watcom and GCC. The last time I tried Borland 5.5 with the
> Euphoria to C translator v2.4 I had a hell of a time trying to get the
> enviromental
> variables set, but once I did though, I did a test compile with window.exw or
> winwire.exw (I forgot which); it translated/compiled, but when I ran it, I got
> a machine exception. They both worked fine with OpenWatcom.
> 
> Perhaps it's better now with v2.5, I havent tried. But since then I've came
> to the conclusion that 99 percent compatable just isnt good enough in some
> cases
> and that only perfect is.
> 
> Maybe you can do some testing with it to see if you can reproduce the problem
> with the 2.5 translator.

window.exw and winwire.exw both run fine when translated/compiled
with the 2.5 translator and Borland. It's not convenient for me
to try 2.4 right now.

When I say that Borland is 99% compatible, I'm just referring
to fairly trivial differences. I don't recall exactly, but
some of the details reported by dir() might be a bit different 
for example. You aren't likely to get a crash because you used 
Borland rather than Watcom (unless there's an error in your code,
such as not declaring a .dll routine as CDECL.)

Regards,
   Rob Craig
   Rapid Deployment Software
   http://www.RapidEuphoria.com