OpenEuphoria

RE: wxEuphoria

• Posted by Matthew Lewis <matthewwalkerlewis at YAHOO.COM> Feb 11, 2003
• 586 views

> From: jbrown1050 at hotpop.com [mailto:jbrown1050 at hotpop.com]



> Linux does C calls the cdecl way, not sure about C++ calls (I 
> didnt finish
> compling wxWindows yet (its been 16 hours so far) so I didn't 
> get to test it
> yet).

I suspect that all calls will be done using cdecl, passing 'this' as the
first parameter.  The thiscall thing seems to be MSVC specific.


> Just Some Notes:
> 
> for cplusplus.e,
> 
> dlopen(x, or_bits(#001, #100)) is the same as LoadLibrary(x)
> dlclose(x) is the same as FreeLibrary(x)
> dlsym(x, y) is the same as GetProcAddress(x, y)
> 
> in wxEuphoria.e,
> 
> user32, xPeekMessage, etc. seem not to be needed. Why were 
> they there in the
> first place?

At some point, I was attempting to make my own message loop.  They never got
deleted.  There's really a lot that needs to be done to make it cross
platform.  First, I think we're going to have to figure out how to import
stuff under linux.  In windows, I can do it by ordinal (and can get a list
of undecorated names using Dependency Walker), but I don't think you can do
this using linux.  And, of course, there's the issue of calling conventions.
 
> those are the only 2 files i've looked at, besides fptr.e
> 
> and, afai can tell, fptr.e's thiscall routines should work just fine
> ... I think.
> However, I have not had the chance to test it yet, as I've ready said.

I suspect that you'll crash and burn using thiscall. :)

Matt Lewis