Silverlight Tip of the Day #40: 1.05 != 1.05 - Peril with Floating Point Comparisons.

presentão de Ano Novo: dúzias de dicas e tutoriais de Silverlight ;)

o UAU nosso de cada dia — Sat, 03 Jan 2009 11:25:46 GMT

essa lista eu copiei desse blog bárbaro (acompanhe por RSS você também): uma lista de dicas super úteis

Silverlight Tips of the Day - Summary Outline

Silverlight Tips of the Day - Blog by Mike Snow — Fri, 02 Jan 2009 22:57:06 GMT

The purpose of this post is to create an outline summary all the blogs from my Silverlight tips of the

Silverlight Tips of the Day - Summary Outline

Silverlight Tips of the Day - Blog by Mike Snow — Fri, 02 Jan 2009 22:57:06 GMT

The purpose of this post is to create an outline summary all the blogs from my Silverlight tips of the

Silverlight Tips of the Day – Week 7

Visual Web Developer Team Blog — Thu, 25 Sep 2008 17:56:16 GMT

Silverlight Tip of the Day #46 Title: Font Support in Silverlight Silverlight Tip of the Day #45: Title:

Silverlight Cream for September 15, 2008 -- #368

Community Blogs — Mon, 15 Sep 2008 19:20:35 GMT

Martin Mihaylov on the DataGrid, Bart Czernicki on Game Concepts, James Bacon on an update to Mashooo

re: Silverlight Tip of the Day #40: 1.05 != 1.05 - Peril with Floating Point Comparisons.

michaeldrotar — Sun, 14 Sep 2008 02:39:08 GMT

Good tip. Floating point comparisons are often a source of frustration.

The examples aren't quite equivalent though. The first one is saying to stop when scaleX is 2.0 and the second is saying to stop when scaleX is greater than 2.0

re: Silverlight Tip of the Day #40: 1.05 != 1.05 - Peril with Floating Point Comparisons.

mike.snow — Sat, 13 Sep 2008 16:20:44 GMT

ZGor - Actually I agree, i'll change it to your solution.

Dew Drop - September 13, 2008 | Alvin Ashcraft's Morning Dew

Dew Drop - September 13, 2008 | Alvin Ashcraft's Morning Dew — Sat, 13 Sep 2008 13:53:20 GMT

Pingback from Dew Drop - September 13, 2008 | Alvin Ashcraft's Morning Dew

re: Silverlight Tip of the Day #40: 1.05 != 1.05 - Peril with Floating Point Comparisons.

zgor — Sat, 13 Sep 2008 12:18:58 GMT

I don't feel comfortable with your alternative solution. It is of course an alternative but I don't want to multiply 0.05 by 40 in mind to get 2.0, my actual loop ending number.

My way would be the following:

scale.ScaleX = 0.0;

while (scale.ScaleX <= 2.0)

{

scale.ScaleX += 0.05;

// Do stuff here...

}

[ you see, we don't have a "40" in the code :) ]

re: Silverlight Tip of the Day #40: 1.05 != 1.05 - Peril with Floating Point Comparisons.

Skyrunner — Fri, 12 Sep 2008 20:17:09 GMT

It's like in any other application.

Floating calcul has always been bad.

float f1 = 0.1f * 0.1f;

float f2 = 0.01f;

if (f1.Equals(f2)) Console.WriteLine("f1 = f2");

Should use float.Epsilon for compare them.

Silverlight Tip of the Day #40: 1.05 != 1.05 - Peril with Floating Point Comparisons.

Blogs — Fri, 12 Sep 2008 17:17:37 GMT

The other day I found a bug in one of my Silverlight applications that was doing floating point comparisons