
Why are you dividing by (xy) when you started with x=y?
You have just been Sharapova'd.





Dominic Burford wrote: x2  y2 = xy  y2.
Dividing by (xy), obtain
x + y = y.
Wrong... aint it?
x2 y2 / (xy) => x+y
xy y2 / (xy) => y+y
xy / xy => 1*1/11 => (actually how could you divide this when there is a minus...)
y2 / xy => y/x1 => (actually how could you devide this when there is a minus...)
But i guess thats bullshit 2 because it "should"? be x2/xy  y2/xy which ruins everything
Okay screw everything... you are wrong, thats all i can say
Rules for the FOSW ![ ^]
if(this.signature != "")
{
MessageBox.Show("This is my signature: " + Environment.NewLine + signature);
}
else
{
MessageBox.Show("404Signature not found");
}





HobbyProggy wrote: xy y2 / (xy) => y+y Nope.
xyy2 = y(xy)
You have just been Sharapova'd.





Ah yeah i started to correct it because i know its not correct you have to divide every part of that equation that leads to funny result
Rules for the FOSW ![ ^]
if(this.signature != "")
{
MessageBox.Show("This is my signature: " + Environment.NewLine + signature);
}
else
{
MessageBox.Show("404Signature not found");
}





if(!string.IsNullOrEmpty(this.signature))
ftfy





Thank god signature is not an object you first have to convert .ToString() right?
Rules for the FOSW ![ ^]
if(this.signature != "")
{
MessageBox.Show("This is my signature: " + Environment.NewLine + signature);
}
else
{
MessageBox.Show("404Signature not found");
}






A high school teacher showed this to me some 10+ years back (feeling old now).
All I can say is no.





The only thing i can agree with is that 1 != 3/3 (at least not exactly) because 1/3 is 0,333... and multiplied with 3 it is just 0,99999.... which is technically 1 but not 100%
Rules for the FOSW ![ ^]
if(this.signature != "")
{
MessageBox.Show("This is my signature: " + Environment.NewLine + signature);
}
else
{
MessageBox.Show("404Signature not found");
}





Quote: 0,99999.... which is technically 1 but not 100% Uh?





Whats the matter ?
Rules for the FOSW ![ ^]
if(this.signature != "")
{
MessageBox.Show("This is my signature: " + Environment.NewLine + signature);
}
else
{
MessageBox.Show("404Signature not found");
}






By definition, not by maths
Rules for the FOSW ![ ^]
if(this.signature != "")
{
MessageBox.Show("This is my signature: " + Environment.NewLine + signature);
}
else
{
MessageBox.Show("404Signature not found");
}





By maths. There's no difference.





Allright, tell that the next flightcomputer that breakes down because he multiplied 0,333 and didn't get to 1
Rules for the FOSW ![ ^]
if(this.signature != "")
{
MessageBox.Show("This is my signature: " + Environment.NewLine + signature);
}
else
{
MessageBox.Show("404Signature not found");
}





You know, float are not real numbers.
(likewise Computer Science is not Mathematics)





CPallini wrote: (likewise Computer Science is not Mathematics)
But its both logic And 0,999 is not 1 it's even written different
But i guess we could debate ages about that
Rules for the FOSW ![ ^]
if(this.signature != "")
{
MessageBox.Show("This is my signature: " + Environment.NewLine + signature);
}
else
{
MessageBox.Show("404Signature not found");
}





Right: we could follow all the nines until we find a difference.





Take your pick: How Can 0.999... = 1?  Purplemath[^]
For example:
x = 0.999...
10x = 9.999...
10x  x = 9.000...
9x = 9
x = 1
EDIT: As Nagy said[^], 2+ hours ago.
"These people looked deep within my soul and assigned me a number based on the order in which I joined."
 Homer





1/6 = 0,166666
>*6
0,9996
x = 0,9996
10x = 9,996
10x x = 8,9964
9x = 8,9964
x = 0,9996
?
Rules for the FOSW ![ ^]
if(this.signature != "")
{
MessageBox.Show("This is my signature: " + Environment.NewLine + signature);
}
else
{
MessageBox.Show("404Signature not found");
}





HobbyProggy wrote: 1/6 = 0,166666
>*6
0,9996
Nope  6 × 0.1666... = 0.9999...
It's simple multiplication:
1 x 6 = 6 (0.6)
6 x 6 = 36 = add 3 to the column on the left (6 + 3 = 9), and put 6 in this column (0.96)
6 x 6 = 36 = add 3 to the column on the left (6 + 3 = 9), and put 6 in this column (0.996)
6 x 6 = 36 = add 3 to the column on the left (6 + 3 = 9), and put 6 in this column (0.9996)
6 x 6 = 36 = add 3 to the column on the left (6 + 3 = 9), and put 6 in this column (0.99996)
etc.
Because you're repeating the operation an infinite number of times, there's no point where you stop and leave the last digit as 6 . There's always another digit to the right which needs to be multiplied by 6 , carrying the 3 into the current column.
"These people looked deep within my soul and assigned me a number based on the order in which I joined."
 Homer





So this works only for 0.999999 ?
Because the 6 at the end is in this case important to show that it wont be a 1 in the end
But nevermind, this is all just playing with numbers
Rules for the FOSW ![ ^]
if(this.signature != "")
{
MessageBox.Show("This is my signature: " + Environment.NewLine + signature);
}
else
{
MessageBox.Show("404Signature not found");
}





HobbyProggy wrote: Because the 6 at the end is ...
But there isn't a 6 at the "end", because there isn't an "end"!
Think of it like this:
using System;
static class Program
{
static void Main()
{
while (true)
{
Console.WriteLine("9");
}
Console.WriteLine("Squirrel!");
}
}
If you run that program, how long will you have to wait before it prints "Squirrel"?
"These people looked deep within my soul and assigned me a number based on the order in which I joined."
 Homer





STACK OVERFLOW
nvm
Rules for the FOSW ![ ^]
if(this.signature != "")
{
MessageBox.Show("This is my signature: " + Environment.NewLine + signature);
}
else
{
MessageBox.Show("404Signature not found");
}





mmm
working by 9, not working by 6
what about 69? does it works?
Oh, wait... I think I stop now since I am about to break the KSS rule
I am still on the way getting my coat
M.D.V.
If something has a solution... Why do we have to worry about?. If it has no solution... For what reason do we have to worry about?
Help me to understand what I'm saying, and I'll explain it better to you
Rating helpful answers is nice, but saying thanks can be even nicer.



