User:Mwn3d/Word mincing: Difference between revisions
(Taking Paddy's "print" suggestion) |
|||
| Line 6: | Line 6: | ||
==Random vs. Pseudo-random== |
==Random vs. Pseudo-random== |
||
I don't think there is a language out there that has a true random number generator built in. When we say "random" in a task we probably mean "pseudo-random". That's just what people call it because saying "pseudo-random" is a mouthful. Unless the task is to create a pseudo-random number generator or receive truly random numbers from a true random number generator (random.org or something), these words are also interchangeable. |
I don't think there is a language out there that has a true random number generator built in. When we say "random" in a task we probably mean "pseudo-random". That's just what people call it because saying "pseudo-random" is a mouthful. Unless the task is to create a pseudo-random number generator or receive truly random numbers from a true random number generator (random.org or something), these words are also interchangeable. |
||
==Print (in the console) vs. print (on paper) vs. print (on a window) vs. show vs. display== |
|||
This is sort of like random/pseudo-random. In general, this means print to standard output (wherever that goes). In tasks which are about printers or GUIs it should be made obvious in the task description which one is required. |
|||
Also, it is ''very'' good practice to show example use and output from an example (where there is output to be shown). Some tasks (like [[Singly-linked list/Element definition]]) simply don't have output, so it doesn't need to be shown. Tasks which require calculation or generation of something should have output shown pretty much no matter what. If the output is long, consider making a separate page for your example and linking to it from the task page (a la [[99 Bottles of Beer/C++/Object Oriented]] and [[99 Bottles of Beer#An object-oriented solution]]). |
|||
More to come as I see/remember similar situations. |
More to come as I see/remember similar situations. |
||
<!-- |
|||
==print and display== |
==print and display== |
||
I know I have been questioned about how to write a task and mean "It is also a requirement of the task to show your output in some meaningful way that doesn't tax the RC servers, on this page as part of a languages submission" |
I know I have been questioned about how to write a task and mean "It is also a requirement of the task to show your output in some meaningful way that doesn't tax the RC servers, on this page as part of a languages submission" |
||
I would prefer to just use the phrase "print and display". --[[User:Paddy3118|Paddy3118]] 08:39, 17 April 2011 (UTC) |
I would prefer to just use the phrase "print and display". --[[User:Paddy3118|Paddy3118]] 08:39, 17 April 2011 (UTC) |
||
--> |
|||
Revision as of 17:00, 17 April 2011
I've noticed a couple instances of people getting too technical. Maybe people are trying to be cute. Maybe they're trolling. Maybe they're just computer programmers and (like computers) they try to take everything literally. In any case, such rigidity gets in the way of lots of things, and I have decided to voice my opinions about some of the more prominent "arguments" as I notice them.
Function vs. Subroutine vs. Method vs. whatever term your language uses for it
For the purposes of tasks on this site, these words are all pretty much interchangeable. Getting all bent out of shape because a task says "function" and you want to do it in assembly or some language where you don't really have a nice way to return a value just gets in the way of things. Do the best you can and note the difference in behavior. If it goes against the intention of the task, then we will discuss it. In general it's probably OK not to match up exactly on little things like that.
Random vs. Pseudo-random
I don't think there is a language out there that has a true random number generator built in. When we say "random" in a task we probably mean "pseudo-random". That's just what people call it because saying "pseudo-random" is a mouthful. Unless the task is to create a pseudo-random number generator or receive truly random numbers from a true random number generator (random.org or something), these words are also interchangeable.
Print (in the console) vs. print (on paper) vs. print (on a window) vs. show vs. display
This is sort of like random/pseudo-random. In general, this means print to standard output (wherever that goes). In tasks which are about printers or GUIs it should be made obvious in the task description which one is required.
Also, it is very good practice to show example use and output from an example (where there is output to be shown). Some tasks (like Singly-linked list/Element definition) simply don't have output, so it doesn't need to be shown. Tasks which require calculation or generation of something should have output shown pretty much no matter what. If the output is long, consider making a separate page for your example and linking to it from the task page (a la 99 Bottles of Beer/C++/Object Oriented and 99 Bottles of Beer#An object-oriented solution).
More to come as I see/remember similar situations.