0 Members and 1 Guest are viewing this topic.
I'll agree with Ashbad that the loss of precision in the third decimal digit will probably confuse some people. Perhaps just a mention of this in the readme would do?
In other news, Frey continues kicking unprecedented levels of ass.
Ok, a few things.That .22 of 7.22? That means that, beyond those 7 decimal digits, only 22% of numbers result in a unique binary value.
Since Axe is a language used mostly by inexperienced programmers that haven't touched face with computer languages like C++ or Java,
Quote from: Ashbad on August 07, 2011, 01:19:03 pmSince Axe is a language used mostly by inexperienced programmers that haven't touched face with computer languages like C++ or Java, BLASPHEMY! I write in C# and use floating points all the time! And I use Axe!
I do see you guys's point with killing the third decimal point simply because the percision isn't offered. I would propose an XXX.XX way of writing numbers so that it isn't confusing why comparisons aren't working, but you can still go all the way up to 255 (an XX.XX would only allow up to 99). Also, another question: will putting a degree sign before a fixed-point decimal variable return the whole number portion of said variable (like int(x) in BASIC)?
Are there any posibillities to calculate with numbers like 3.58264579835 so that it uses the 3.58... but tells you 4 if ypu check the number?
Also, people seem to be using different notations. Using "AAA.BBB" to mean AAA + BBB/256 is not how numbers are normally expressed. As far as I was aware, this was going to be straightforward decimal notation, where "AAA.BBB" means AAA + BBB/1000, rounded to the nearest 256th.Edit: the unconventional notation would also make it more confusing for beginners, by the way.
There's absolutely no way you could specify the integer part from 0-999 unless you did 10.6 fixed point instead of 8.8, which is what Axe uses Also, given that Axe treats all fixed-point numbers as signed, the integer part can only be from -128 to 127, anyway.
Ah, I see. Yeah, that's confusing, though