Talk:Count in octal: Difference between revisions
Content added Content deleted
(→Dupe?) |
(number conversion is not a requirement of this task) |
||
| Line 8: | Line 8: | ||
:::Be careful with your modifiers. We have plenty of good tasks that run for "a really long time"/"forever". [[Lucas-Lehmer test]] and [[Loops/Infinite]] are good examples. In any case, if the range were smaller I would still call it a duplicate. --[[User:Mwn3d|Mwn3d]] 20:10, 6 June 2011 (UTC) |
:::Be careful with your modifiers. We have plenty of good tasks that run for "a really long time"/"forever". [[Lucas-Lehmer test]] and [[Loops/Infinite]] are good examples. In any case, if the range were smaller I would still call it a duplicate. --[[User:Mwn3d|Mwn3d]] 20:10, 6 June 2011 (UTC) |
||
:::: I do not like those tasks either. That said, "forever" really means "until interrupted". --[[User:Rdm|Rdm]] 20:18, 6 June 2011 (UTC) |
:::: I do not like those tasks either. That said, "forever" really means "until interrupted". --[[User:Rdm|Rdm]] 20:18, 6 June 2011 (UTC) |
||
:The other task mentions number conversion routines. For this task it may be possible to use native octal, rather than number conversion. However, this is not a requirement, so if the language does not support octal, then number conversion is permitted. IMHO It is better to split the common bases (hex,dec,oct,bin) into separate tasks, rather than having one task to implement them all, because a dedicated implementation may be smaller and more efficient than a multibase implementation, so if you are writing an application that has a primary purpose of dealing with octal numbers, it would be better to use dedicated octal number manipulation routines. --[[User:Markhobley|Markhobley]] 20:35, 6 June 2011 (UTC) |
|||
Revision as of 20:35, 6 June 2011
Dupe?
Now that I think about it, I think this task is covered by Non-decimal radices/Output. I know there's no "loop forever" in that task, but I think it covers the meat of this task (and more). Thoughts? --Mwn3d 03:47, 6 June 2011 (UTC)
- Hmm... Seems like it. The "loop over every integer" bit isn't completely trivial, but yeah, it's probably not enough to differentiate this. MagiMaster 03:50, 6 June 2011 (UTC)
- The "loop over every integer" requirement is also not practical to implement. 4 billion lines (on a 32 bit machine) might be doable, in terms of time to display -- I am not sure if anyone has the patience to sit through a display of 4 billion lines, but hypothetically speaking a reasonably fast machine could complete this task. However, on a 64 bit machine, you will die of old age before the task completes. And, in my opinion, any task which requires the programmer be dead before the task completes is a bad task. --Rdm 20:04, 6 June 2011 (UTC)
- Be careful with your modifiers. We have plenty of good tasks that run for "a really long time"/"forever". Lucas-Lehmer test and Loops/Infinite are good examples. In any case, if the range were smaller I would still call it a duplicate. --Mwn3d 20:10, 6 June 2011 (UTC)
- I do not like those tasks either. That said, "forever" really means "until interrupted". --Rdm 20:18, 6 June 2011 (UTC)
- Be careful with your modifiers. We have plenty of good tasks that run for "a really long time"/"forever". Lucas-Lehmer test and Loops/Infinite are good examples. In any case, if the range were smaller I would still call it a duplicate. --Mwn3d 20:10, 6 June 2011 (UTC)
- The "loop over every integer" requirement is also not practical to implement. 4 billion lines (on a 32 bit machine) might be doable, in terms of time to display -- I am not sure if anyone has the patience to sit through a display of 4 billion lines, but hypothetically speaking a reasonably fast machine could complete this task. However, on a 64 bit machine, you will die of old age before the task completes. And, in my opinion, any task which requires the programmer be dead before the task completes is a bad task. --Rdm 20:04, 6 June 2011 (UTC)
- The other task mentions number conversion routines. For this task it may be possible to use native octal, rather than number conversion. However, this is not a requirement, so if the language does not support octal, then number conversion is permitted. IMHO It is better to split the common bases (hex,dec,oct,bin) into separate tasks, rather than having one task to implement them all, because a dedicated implementation may be smaller and more efficient than a multibase implementation, so if you are writing an application that has a primary purpose of dealing with octal numbers, it would be better to use dedicated octal number manipulation routines. --Markhobley 20:35, 6 June 2011 (UTC)