Rosetta Code/Tasks sorted by average lines of code: Difference between revisions

m
Typos
m (omit)
m (Typos)
Line 1:
{{alertbox|#ffe4e4|Note that it is not necessarily the case that this task represents a sensible concept for Rosetta Code, as it may well be promoting an anti-pattern. As such, please do not attempt it until [[Talk:Rosetta Code/Tasks sorted by average lines of code|discussion]] fully resolves this issue.}}
As such, please do not attempt it until [[Talk:Rosetta Code/Tasks sorted by average lines of code|discussion]] fully resolves this issue.}}
{{draft task|Rosetta Code related}}
Tasks in Rosetta Code in generally are simple tasks, yet they still lie in a range of complexity spectrum. By sortng tasks in term of its complexity, a new code contributer may found more comfortable to sumbit code in order from simple task to more complex one. An intuitive complexity indicator may be the average number of lines of code for the tasks.
By sorting tasks in term of its complexity, a new code contributer may find himself more comfortable to submit code in order from simple task to more complex one. An intuitive complexity indicator may be the average number of lines of code for the tasks.
 
'''Task:'''
<br>
Sort the tasks in Rosetta Code in ascending order of average lines of code. Some issues to be aware of:
Some issues to be aware of:
# It may be difficult to identify a code block from raw html source;
# Some languages may provide multiple demonstrations, average should be made per demonstration rather than per language.
Anonymous user