Re: ObjC++ (& Scary Carbon Stuff)
Re: ObjC++ (& Scary Carbon Stuff)
- Subject: Re: ObjC++ (& Scary Carbon Stuff)
- From: Chris Thomas <email@hidden>
- Date: Wed, 05 Dec 2001 14:16:10 -0800
On 12/5/01 1:01 PM, "Thomas Lachand-Robert" <email@hidden> wrote:
>
Eeeeeh... Sorry but I'm still scared... particularly because you seem
>
unsure about your own code, because of (*(FileInfo
>
*)&catalogInfo.finderInfo) and 'evilHasComeToGetUs' does not make things
>
better.
No, I'm absolutely sure about my code; it's my memory that I'm unsure of.
Were I to type the pure-Cocoa solution, I'd also have to look up the
constant names. Please read my message again. I don't care whether you use
Carbon or Cocoa (they'll both continue to be supported for a long time to
come, so do whatever you like), my point is simply that your code was wrong.
If you found it in Apple's documentation, it's a bug in the documentation
that should be fixed. If not, it's a bug in your code that should be fixed.
Either way, it's not a fair example.
There are valid reasons listed in my message for avoiding the pure-Cocoa
solution (have to run on 10.0, need more info than type and creator).
Without those constraints, I would use the pure Cocoa solution.
And evil coming to get us always makes things better.
Chris