Re: adding Foundation framework to a Carbon application
Re: adding Foundation framework to a Carbon application
- Subject: Re: adding Foundation framework to a Carbon application
- From: Chris Parker <email@hidden>
- Date: Sat, 19 Nov 2005 12:02:55 -0800
On Nov 19, 2005, at 11:44 AM, Ed Voas wrote:
Ugh. Bad answer. No cookie. :-P Renaming files to appease the
compiler sucks as you might lose all your cvs history, etc. (of
course, if you use Perforce, it's not as much of an issue, but it
does mean you have to 'integrate' to create a new file).
There's actually a popup in the info window if you get info on the
file you want to include your obj-c stuff in. Just select the
"sourcecode.cpp.objcpp" or "sourcecode.c.objc" option.
Ah, yup. I completely forgot about the version control issue. If
you're using CVS, this is a problem - subversion & Perforce less so.
If this -is- an issue, then switching your file to compile as
Objective-C as Ed suggests here is better.
While I really don't like file extensions as type indicators that
much in general, for development I like having the extension match
the language - I can tell immediately what the file -should- be
compiled as from the Finder or 'ls', rather than having to poke at
the project settings in Xcode to figure out what the compiler's going
to do with it.
I don't think it's a -bad- answer, though. :) As with many questions
asked here, there are a lot of things to consider that are unique to
the context they're asked in and neither of us know everything about
Don's setup or how he likes to work.
.chris
--
Chris Parker
Cocoa Frameworks
Apple Computer, Inc.
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Cocoa-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden