Re: Casting anonymous Objects leads to different values on getter functions (while getting no warnings at compile time)
Re: Casting anonymous Objects leads to different values on getter functions (while getting no warnings at compile time)
- Subject: Re: Casting anonymous Objects leads to different values on getter functions (while getting no warnings at compile time)
- From: Martin Wilz <email@hidden>
- Date: Tue, 8 Nov 2005 11:06:49 +0100
Hi Pontus, Hi Hauke, Hi Pascal,
first I'd like to thank you for your feedback on the internals of this
problem. So I grok, that the method is dynamically resolved at run
time while the method signature is fixed at compile time.
> MHO, you are not supposed to use the same message name with different type signatures
The point I wanted to get through is that you don't have the
possibility to check for every other object method in the used
frameworks, if you don't get any warnings about collisions. Otherwise
I don't think you should restrict programmers in their naming schemes.
Concerning the warning issue, I was not able to locate a switch in the
preferences to enable these in XCode 2.1. I also opened the project on
an freshly installed version, so the switch (if it exists) is off by
default or already encoded into the project that was also created
without touching the project preferences.
with Regards,
Martin
_______________________________________________
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