Quote Originally Posted by SyntaX****** View Post
To most it would seem useless, so it is mainly for those who have a deeper understanding of programming precision restrictions.

Try to enter this number into any calculator program:
Code:
*7*76****4862**5*0772**05**078*0247**6*7*76*78*42*065727*4*008**577*2675805500*6***2708477*224075*602**20***87*87*****5765878*7688*44*66224*28474*06**474*24*777678**424865485276*022**60*2460*4***45*082*520850057688*8*50682*4246288*47******05408272*7*6**505*06845862*82***47245**847*7*6*048*5*56*2*624224**72*5
If you are on a windows machine you will hear crazy error beeps. I'm not sure how other OS calculators handle the number but the decimal precision is cut wayyyy short most of the time.

To give you a better example. Its like me saying 2+2=5 (Then saying, "well I was close!"). This is how most calculators and computers handle numbers when they get too large. I'm providing EXACT calculations :-)

Another example: Enter **52*2*504606846*76 into your calculator (which is 2^60). Now do the binary conversion and you will probably get something like *.^+****00. Inaccurate! Now enter that same number into my calculator. You will get the exact binary equivalent which is: *000000000000000000000000000000000000000000000000000000000000

~SyntaX
Hmm, I never thought of it that way, but it still is useless to me, sorry

But one day I might find it useful, so thanks in advance.