Mike Hore wrote:
> Erik wrote:
>
> > Well, according to Google groups, this will be the first post of
the
> > year, so: First Post! Woo-Hoo!
>
> Not here -- it's the 2nd here by now. Maybe in your time zone...
Damn! That's right, you're 24 hours ahead of us, aren't you? Ah
well...
> It's probably "just" a matter of working out what actual functions
> to call. Certainly the ObjC sequence is constructed of a series
> of low-level calls. C++ would probably be similar though I haven't
> really looked into it. But once you know the low-level calls, you
> just call them. The ABI for simple calls is pretty standard across
> PowerPC languages (though I suspect there may be minor differences
> with floating-point parameters).
You know, I recall some time back checking out Apple's docs on
ObjC (sorry, can't remember the exact webpage or general
section; it was on Objective C and shared library generation, I
think). On this particular page, Apple actually warned against using
C++ for shared libraries. Something about how each C++ compiler
sort of does its own thing, so there's no standard way of calling
functions or objects unless you interject a layer of C code. Don't
know if this relates to the Cocoa framework in any way or it's
just a general C++ issue, though.
I'll try something with XCode sometime this weekend and see
what happens. I've been meaning to play with it any way. (It would
be interesting if XCode did one thing, and Codewarrior did another...)
Erik
|
