Yes, we all agree Colloden should be lynched by the JREF mob for posting a "Simple" mathmatical problem (?).geni said:Do we really have an agreement here?
I propose we chalk it up to a misunderstanding of terminology and I take back all the mean things I said about you.LuxFerum: Thanks for your time![]()
no problemxouper said:I propose we chalk it up to a misunderstanding of terminology and I take back all the mean things I said about you.![]()
You just get used to it.ceptimus said:It gets easier to back down as you get older.![]()
Since I seem to be the only one who got pissed off and everyone else kept their cool, the problem is obviously not your fault. In fact, looking back at my participation in this thread, I'm inspired that others were able to remain civil and it's obviously something I need to work on.LuxFerum: Sorry for pissing you off![]()
subscripts t<sub>i</sub> yields t<sub>i</sub>TillEulenspiegel said:Hey Walter,
What were you using to get the subsets in your post? I tried to cut n paste from maythtype but iy didn't work.
Earthborn said:Think of it this way:
What is the difference between 1 and 0.999(recurring)? The difference is infinitely close to 0, or in other words, the two are indistinguishable.
If 0.999(recurring) isn't 1 what on earth could it be? Is there a difference?
sorgoth: There's a difference, it's just infinitely small. Does it matter? Will it change anything? No, but it's still different. Anyway, having 9.999...... In actual things is impossible, as you can't get infinitely small.
Here we go again. How did you get the code to appear instead of performing its function?Walter Wayne said:subscripts t<sub>i</sub> yields t<sub>i</sub>
superscripts t<sup>i</sup> yields t<sup>i</sup>t
Ahhh so you have to use the BBS script and not a native application?Walter Wayne said:
subscripts t<sub>i</sub> yields t<sub>i</sub>
superscripts t<sup>i</sup> yields t<sup>i</sup>
Also, if you see someone doing something you want to imitate, the most reliable method is to hit the quote button, and see how they did it in there post.
xouper posted about this somewhere in the Forum Help section I think, but I'm to lazy to find it.
Walt
WHAT flaw in my reasoning? I have shown that there are indeed an infinite number of points that are NEAR unity that are precisely NOT unity. That for any arbitrary point near one, there is one nearer. One of these points is 0.9~ (as we describe it in the decimal system). A "closer" one would probably be 0.F~16.aerosolben said:Don't you see the flaw in your reasoning? This would mean that there's a number larger than infinity, which is impossible by definition. Therefore, you cannot treat infinity the way you have been treating it. You must treat it as a limit to think of it infinitely rather than finitely.
Example: If we define a > 0 such that
a = 1 - 0.9~ (infinity nines)
we can also define b such that:
b = a/10 = 1 - 0.9~ (infinity+1 nines)
But infinity+1 does not exist! This is completely impossible! Therefore, a cannot be greater than 0; the only possible value for a is 0, such that a = b.
not there yet
|
| not there yet
| |
| |
0,999...---Look the 3 little dots, we are there now, forget what we said before.
|
|
|
Still
not
there
Agreed. That's true of any real number.Zep: I have shown that there are indeed an infinite number of points that are NEAR unity that are precisely NOT unity. That for any arbitrary point near one, there is one nearer.
You haven't shown that 0.999... is not equal to one.One of these points is 0.9~ (as we describe it in the decimal system).
Wrong. The hexadecimal number 0.FFF... is exactly equal to the decimal number 0.999...A "closer" one would probably be 0.F~16.
Perhaps the solution is to read the number from right to left then?LuxFerum said:I think the problem of that notation is that it mixes the process with the limit.
Basicaly like this.
Code:not there yet | | not there yet | | | | 0,999...---Look the 3 little dots, we are there now, forget what we said before. | | | Still not there