Rosetta Code:Add a Task: Difference between revisions

Add prologue, syntax, add to "example code" section and remove stub.
m (typo)
(Add prologue, syntax, add to "example code" section and remove stub.)
Line 1:
{{stub}}<!-- prologue. Feel free to help fill this page out; you guys tend to refine this more than I do. This is (currently) mostly a brain dump of my general lines of preference embedded in a structured outline.-->So you want to see a problem tackled, and you know enough about it that you can write a solution or two yourself. If you're beyond simply [[Rosetta Code:Village Pump/Suggest a programming task|suggesting a task]], you can add one yourself.
 
A task has a very simple layout:
<!-- Need discussion of task syntax -->
<pre>{{task}}Description of the task
 
...
 
Examples</pre>
==Prerequisites==
===Draft vs non-draft===
Line 41 ⟶ 46:
===Example code===
It is usually a good idea to '''have at least one example implementation completed, tested, and working''' ''before'' you start writing the description of the task, as well as '''a sample of correct output.''' It is usually a good idea if this first example shows its output; even if it isn't strictly necessary for the completion of the task, it helps other implementers understand the task and what they need to do.
 
In short, solve your own task. Show us how it's done.
 
==Additional information==