Re: thin linking: "file is not of required architecture"
Re: thin linking: "file is not of required architecture"
- Subject: Re: thin linking: "file is not of required architecture"
- From: "Sherm Pendley" <email@hidden>
- Date: Mon, 21 Apr 2008 12:08:29 -0400
On Mon, Apr 21, 2008 at 11:37 AM, Steve Checkoway <
email@hidden> wrote:
I haven't been following this at all, but I have no idea what you mean by bsd calling conventions vs. ansi-c calling conventions vs objective-c calling conventions. A function call convention is generally something that the hardware specifies. See <http://compilers.iecc.com/comparch/article/03-02-079>.
Calling conventions are a mix of hardware and language specification.
The hardware specifies how the stack frame is arranged, how parameters are passed, and return values returned. But, symbol naming conventions are left up to language standards - C++, for example, "mangles" method and function names to include the type signature, so as to turn overloaded methods into unique names that the linker can handle. Objective-C does something similar to create IMP function names from methods, adding a prefix and swapping _s for :s.
For more, have a look: <
http://en.wikipedia.org/wiki/Name_mangling>
sherm--
--
Cocoa programming in Perl:
http://camelbones.sourceforge.net
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden