Talk:Decimal floating point number to binary: Difference between revisions
Content added Content deleted
(→input: answer) |
(→Task Title: new section) |
||
Line 29: | Line 29: | ||
:Is there something wrong with the examples given (23.34375 => 10111.01011, 1011.11101 => 11.90625)? Note that PI is of course always going to be an approximation and therefore likely to be inconsistent even between 32/64 bit versions of the same language. One thing I spotted worth checking is that it does not go into an infinite loop for eg 1/3. --[[User:Petelomax|Pete Lomax]] ([[User talk:Petelomax|talk]]) 13:54, 26 July 2019 (UTC) |
:Is there something wrong with the examples given (23.34375 => 10111.01011, 1011.11101 => 11.90625)? Note that PI is of course always going to be an approximation and therefore likely to be inconsistent even between 32/64 bit versions of the same language. One thing I spotted worth checking is that it does not go into an infinite loop for eg 1/3. --[[User:Petelomax|Pete Lomax]] ([[User talk:Petelomax|talk]]) 13:54, 26 July 2019 (UTC) |
||
:: the examples are ok, but maybe a set of examples, the same for all languages, would be better when one wants to compare results. --[[User:Adam majewski|Adam majewski]] ([[User talk:Adam majewski|talk]]) 14:46, 26 July 2019 (UTC) |
:: the examples are ok, but maybe a set of examples, the same for all languages, would be better when one wants to compare results. --[[User:Adam majewski|Adam majewski]] ([[User talk:Adam majewski|talk]]) 14:46, 26 July 2019 (UTC) |
||
== Task Title == |
|||
Suggest changing the task title to "Decimal Number to Binary". The floating point in the task description is redundant and misleading. |
|||
--[[User:DavidFashion|DavidFashion]] ([[User talk:DavidFashion|talk]]) 19:42, 24 February 2020 (UTC) |