Re: Multiple Inheritence (Was: Is _objc_flush_caches_(Class) necessary to swizzle methods?)
Re: Multiple Inheritence (Was: Is _objc_flush_caches_(Class) necessary to swizzle methods?)
- Subject: Re: Multiple Inheritence (Was: Is _objc_flush_caches_(Class) necessary to swizzle methods?)
- From: DumberThanDanQuayle <email@hidden>
- Date: Sat, 25 Sep 2004 10:10:37 -0400
On Sep 25, 2004, at 8:40 AM, DumberThanDanQuayle wrote:
So far the only down side looks like the compilation errors and
warnings are not marked directly on the methods included but rather at
the "#import" directive. Likewise, there may be problems with the
debugger indicating which line is executing or crashed, but I have yet
to test that issue. Furthermore, while I would rather have some
formal mechanism to deal with those issues, I can easily live with
them or work around them by temporarily placing my method
implementations into a proper class.
This is a note on the issue of XCode's (v 1.5) reaction to the use of
"#include" with *.m method implementation files. While it still
appears true the complier error and warnings are symbolically marked in
the gutter next to the "#include" directive, in the "Detailed Build
Results" window clicking on the individual compilation problems takes
you directly into the problem line in *.m file. So this actually works
just like a header a file. It remains to be seen whether the debugger
will cooperate as well, but it now looks like it might.
_______________________________________________
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