Bug 14090 - Source Analysis issue
Summary: Source Analysis issue
Status: RESOLVED FEATURE
Alias: None
Product: Xamarin Studio
Classification: Desktop
Component: C# Binding ()
Version: 4.0.12
Hardware: Macintosh Mac OS
: --- normal
Target Milestone: master
Assignee: Mike Krüger
URL:
Depends on:
Blocks:
 
Reported: 2013-08-19 16:21 UTC by Neal
Modified: 2013-08-20 01:02 UTC (History)
1 user (show)

Tags:
Is this bug a regression?: ---
Last known good build:

Notice (2018-05-24): bugzilla.xamarin.com is now in read-only mode.

Please join us on Visual Studio Developer Community and in the Xamarin and Mono organizations on GitHub to continue tracking issues. Bugzilla will remain available for reference in read-only mode. We will continue to work on open Bugzilla bugs, copy them to the new locations as needed for follow-up, and add the new items under Related Links.

Our sincere thanks to everyone who has contributed on this bug tracker over the years. Thanks also for your understanding as we make these adjustments and improvements for the future.


Please create a new report on Developer Community or GitHub with your current version information, steps to reproduce, and relevant error messages or log files if you are hitting an issue that looks similar to this resolved bug and you do not yet see a matching new report.

Related Links:
Status:
RESOLVED FEATURE

Description Neal 2013-08-19 16:21:16 UTC
I have the following code:

if (SyncStatusProgressBar.Alpha == 0)
                return;

I'm getting a suggestion of:  WARNING:  Compare a difference with EPSILON

Not sure what the heck that is, I tried applying the fix to see and that didn't work and CMD + Z didn't reverse the fix either which may be another bug if fixes are not registering with UNDO.
Comment 1 Mike Krüger 2013-08-20 01:02:45 UTC
The undo not working is a bug in the 4.0.x versions - should work in the 4.1.x lane.

The issue is right - due to rounding problems it's not recommended using equality operators on floating point numbers. Many users are not aware of these numerical problems.

Microsoft has a good overview of this problem in their docs. But I need to improve the message of this issue - it's one I got contributed and didn't review yet.

For more info about that see:
http://msdn.microsoft.com/en-us/library/ya2zha7s.aspx