Talk:Sum digits of an integer: Difference between revisions
→Input base
m (→Output base: typo) |
|||
| (4 intermediate revisions by 3 users not shown) | |||
Line 9:
:::: I've rewritten “0xfe” to “<code>fe</code><sub><code>16</code></sub>” in the task description; the issue with it before was that “0xfe” is just an encoding of the number (in a way that happens to be a numeric constant in many languages) and not the number itself. In particular, “x” isn't a hex digit. –[[User:Dkf|Donal Fellows]] 08:55, 31 July 2012 (UTC)
== Input base ==
Does the input base matter at all? No matter what the base is, the digit 1 has value 1, 2 means 2, ... a means 10, ... z means 35. Unless we're expected to throw an error if the input contains a digit that is not valid for the given base, I don't see the point of specifying one? --[[User:Markjreed|Markjreed]] ([[User talk:Markjreed|talk]]) 02:10, 30 January 2015 (UTC)
:10 in binary does not equal 10 in hexadecimal, so unless the input is a single digit, yes, it does need to be specified. -- [[User:Eriksiers|Erik Siers]] ([[User talk:Eriksiers|talk]]) 03:38, 30 January 2015 (UTC)
::But the sum of the '''binary''' ''digits' 10 expressed as a decimal is the sum of ''digits'' 10 in ''any'' valid base when expressed as a decimal, i.e. a one plus a zero equals one! --[[User:Paddy3118|Paddy3118]] ([[User talk:Paddy3118|talk]]) 06:59, 30 January 2015 (UTC)
:The input BASE parameter defines how the function interprets the number. Within the computer 0xfe or 254 would both have the same binary representation. I hope that SumDigits(0xfe, 10) would return 11 and that SumDigits(254, 16) would return 29. In the example above in base 35 z would sum to z (35 in base 10), z in base 10 (35) would sum to 8.--[[User:Nigel Galloway|Nigel Galloway]] ([[User talk:Nigel Galloway|talk]]) 14:16, 30 January 2015 (UTC)
| |||