Re: Foundation vs Core Foundation
Re: Foundation vs Core Foundation
- Subject: Re: Foundation vs Core Foundation
- From: Sherm Pendley <email@hidden>
- Date: Mon, 29 Nov 2010 15:19:18 -0500
On Mon, Nov 29, 2010 at 2:59 PM, Jon Sigman <email@hidden> wrote:
>
> Before I start down the wrong path: What is the difference between a Foundation
> tool and a Core Foundation tool?
You mean, the project types when you start a new project in Xcode?
A Core Foundation tool links against (you guessed it)
CoreFoundation.framework, and starts you off with a .c file that
#includes <CoreFoundation/CoreFoundation.h>. A Foundation tool also
links against (another big surprise here) Foundation.framework and
libobjc, and it starts you off with a .m file that #imports
<Foundation/Foundation.h>.
> Primarily I will be needing to use TCP/IP
> sockets, file I/O, and multithreading, so is one a better fit than the other?
Both frameworks have similar capabilities in this regard - the
question is what language you want to use. Core Foundation exposes a C
API; Foundation, an Objective-C API. The latter is a bit higher level,
so you'll sometimes find Foundation-based code also calling various CF
functions when it needs more detailed, lower-level access to something
that's abstracted in Foundation.
Honestly though, if you have working Unix-style code that uses BSD
sockets, file descriptors, and pthreads functions, why rewrite it? Mac
OS X *is* Unix, after all - for something like you're describing, I'd
expect very few changes required to either the code or the make file.
You could probably use it mostly as-is, and simply write a launchd
plist to replace the init script that Solaris uses.
sherm--
--
Cocoa programming in Perl:
http://camelbones.sourceforge.net
_______________________________________________
Cocoa-dev mailing list (email@hidden)
Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden