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: Ondra Cada <email@hidden>
- Date: Sat, 25 Sep 2004 17:17:57 +0200
On 25.9.2004, at 17:06, DumberThanDanQuayle wrote:
To change somewhat the behaviour in future without recompilation
(using techniques like poseAsClassing or categories) would be quite
on the ugly side.
Why would "#include" code be treated differently then normal code is
these cases? I would assume that the compilation warnings and
debugger functions would be more liimted with "#define," but that the
Obj-C runtime would treat "#define" code as normal code to the extent
that you are suggesting "#include" code would be handled differently.
Can you comment on the use of "#define" versus "#include" in a
technique like this?
Nope, macros and your technique are quite equivalent (more or less,
your trick is actually just a poor man's macro processor).
Both macros and including code (and any other technique whose result is
more copies of the same code, like copy'n'paste programming) share the
mentioned problems.
---
Ondra Čada
OCSoftware: email@hidden http://www.ocs.cz
private email@hidden http://www.ocs.cz/oc
Attachment:
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________
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