Re: Interesting behavior of double.NaN
Per Bolmstedt <[email protected]> Tue, 24 Mar 2009 04:56:51 -0400
| Newsgroups | gmane.comp.windows.devel.dotnet.advanced |
|---|---|
| Message-ID | <LISTSERV%[email protected]> |
On Tue, 24 Mar 2009 09:43:20 +0100, Brink, Paul ten <[email protected]> wrote: > Thanks, John, I was aware of this. But I am using this comparison > in a property setter where you normally take some action if the > new property value is not equal to the previous property value. This sounds like an abuse of the equality test that's now come back to bite you. Some modifiable items may have equality check implementations with even more unexpected behavior than doubles. Wouldn't it be possible for you to use an "IsModified" strategy instead? =================================== View archives and manage your subscription(s) at http://peach.ease.lsoft.com/archives