OpenEuphoria

Re: ECW weird behavior

• Posted by "Elliott S. de Andrade" <quantum_analyst at hotmail.com> Oct 21, 2005
• 493 views

>From: Andr=E9 Drummond <guest at RapidEuphoria.com>
>Reply-To: EUforum at topica.com
>To: EUforum at topica.com
>Subject: Re: ECW weird behavior
>Date: Wed, 19 Oct 2005 06:07:36 -0700
>
>posted by: Andr=E9 Drummond <andre_drummond at bol.com.br>
>
> > The solution is to add a "+" sign to all the define_c_func/proc
> > calls that you depend on. e.g. in gd.e:
> >   GdImageCreateFromGif = define_c_func(GD_LIB, "gdImageCreateFromGif"=
,
>...
> > becomes:
> >   GdImageCreateFromGif = define_c_func(GD_LIB, "+gdImageCreateFromGif=
",
>...
> >
> > Also fclose() etc.
> >
> > You should let the author know about it.
> >
> > Regards,
> >    Rob Craig
> >    Rapid Deployment Software
> >    <a=20
>href="http://www.RapidEuphoria.com">http://www.RapidEuphoria.com</a>
> >
>
>Hi Robert,
>
>I=B4ve put "+"s in all define_c_func and define_c_proc the way you've said=
.
>But the problem stills persists.
>
>Now, I am out of tricks... what else can we try?

   The GD library was compiled with the stdcall convention, so only the C=

Runtime functions (fopen, fclose, etc) needed to be designated as cdecl. I=

have posted an update that should fix this and the atan2 domain error that=

sometimes occurs. It seems to work correctly with the free translator and=

Borland.

>
>Andr=E9 Drummond
>


~[ WingZone ]~
http://wingzone.tripod.com/