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: Daniel Jalkut <email@hidden>
- Date: Sat, 19 Nov 2005 17:40:56 -0500
The real problem here is that ObjectiveC uses custom compiler
features and custom file extension for source files, yet shares a
".h" for header files with C.
If Objective-C based header files had a custom header file extension,
the compiler could quickly warn you when you included an Objective-C
file from a straight-C source file, instead of waiting until you
encounter some cryptic language-specific error.
I don't think anybody really minds coaxing the right compiler
features for a particular file, it's just annoying to remember how to
do it if it only comes up once every few months in the form of a
million "what's @class !??!" errors.
Daniel
On Nov 19, 2005, at 5:34 PM, Markus Hitter wrote:
Am 19.11.2005 um 21:19 schrieb Ed Voas:
if it's mostly c++ say, stamping it .m because it might call one
NS function (or merely happen to include an objc header) seems
like a bit much.
Digital computers are machines using _exact_ logic. A single
expression of Obj-C requires you to use a compiler understanding
this language.
There's always extern{} and #ifdef, though.
Markus
- - - - - - - - - - - - - - - - - - -
Dipl. Ing. Markus Hitter
http://www.jump-ing.de/
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Cocoa-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
sweater.com
This email sent to email@hidden
_______________________________________________
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