Re: Assignment problem with doubles: turning into NaN under Leopard
Re: Assignment problem with doubles: turning into NaN under Leopard
- Subject: Re: Assignment problem with doubles: turning into NaN under Leopard
- From: Alastair Houghton <email@hidden>
- Date: Fri, 7 Dec 2007 10:31:02 +0000
On 6 Dec 2007, at 19:29, Frank Illenberger wrote:
John,
in my application, I certainly have an interface declaration for the
method and I therefore don't get any warnings. Even in this example,
the "methodValue" method stands before the caller. The problem does
not seem to be trivial.
Can you show us the actual code that's triggering this problem?
Presumably the example you gave does not (since you state that test
cases don't reproduce the problem). Also, check whether you have any
#defines that might interfere with things. For instance, if between
the two methods you gave as an example, someone did
#define methodValue foo
then it might give the kind of results you're reporting.
Also, try adjusting your compiler settings and see if e.g. turning off
optimizations fixes the problem. In particular, if you have set any
settings in your application but not in your test cases, try changing
those specific settings.
Kind regards,
Alastair.
--
http://alastairs-place.net
_______________________________________________
Cocoa-dev mailing list (email@hidden)
Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden