Talk:Binary digits: Difference between revisions

→‎Has to be a dupe: Terminology clarification
("Binary digits" refers specifically to the digits zero and one.)
(→‎Has to be a dupe: Terminology clarification)
Line 3:
[[Non-decimal radices/Convert]] and [[Non-decimal radices/Output]] cover both built-in functions and user-defined functions. I don't see how this can't be a duplicate. --[[User:Mwn3d|Mwn3d]] 17:29, 6 July 2011 (UTC)
 
:Ok: [[Non-decimal radices/Convert]] - This tasks involve conversion. The binary digits task does not necessarynecessarily involve conversion (unless this is required by the language)
:The [[Non-decimal radices/Output]] requires native support for binary without conversion. The binary digits task does not require native binary support and conversion is allowed.
:So this task is not a duplicate of either task[[User:Markhobley|Markhobley]] 17:40, 6 July 2011 (UTC)
Line 28:
:::: As a friend of mine observed, the intent seems to be to implement a special-case of those other two tasks, without incurring the overhead of generalization. --[[User:Short Circuit|Michael Mol]] 14:35, 7 July 2011 (UTC)
:::::If that's the intent then it needs to be specified better and possibly moved so that the intention is better conveyed (I'm thinking [[Non-decimal radices/Convert/Binary]]). Since [[Non-decimal radices/Output]] doesn't offer much in the way of customization (since the task is to let the language do it), its binary examples would be directly copied to this task. So I think we should disallow those sorts of built-in functions. --[[User:Mwn3d|Mwn3d]] 14:45, 7 July 2011 (UTC)
::::::Possibly we could drop convert, and have Non-decimal radices/Binary, because this task does not necessarynecessarily involve conversion, but I think the name does not need changing here. The task is appropriately categorized. I suggest that we do not rename. [[User:Markhobley|Markhobley]] 15:56, 7 July 2011 (UTC)
:::::::For what it's worth: the J implementation of this task is all about conversion, and not at all about output (since implicit output was sufficient). Furthermore, in the general context of computer engineering, "binary output" typically means something very different from what this task asks for (and is typically machine specific and not general to all the platforms supported by a language unless the language itself only has implementations for one machine architecture). I do not have any specific suggestions to resolve these issues, but I do not think that these issues should be disregarded when considering other suggestions. --[[User:Rdm|Rdm]] 16:50, 7 July 2011 (UTC)
::::::::"Binary digits" refers specifically to set of digits consisting of 0 and 1. [[User:Markhobley|Markhobley]] 17:02, 7 July 2011 (UTC)
:::::::I think we need some terminology clarification here because you seem to be using some words differently than other people. "Native" means "built in to the language" when you say it, right (see [[wp:Native#Computing]] for what other people may be thinking)? Is the Java example of Integer.toBinaryString native? I can't tell what you mean when you say "conversion". Do you mean "changed to a different number"? Do you mean "changed to a different type"? I'm unclear on what "conversion" entails. --[[User:Mwn3d|Mwn3d]] 17:43, 7 July 2011 (UTC)
Anonymous user