Rosetta Code talk:Village Pump/Suggest a programming task: Difference between revisions

(→‎Task guidelines?: Retiring tasks)
Line 17:
:::We've got ''way'' too much structured code on RC. I need to create a task solvable only by goto.. ;-)
:::Rather than promoting pages to the Solutions By Task page, why don't we move them to a "Retired" subcategory? Sadly, though, this means we're going to need some sort of approval process. Gah. Procedures and rules. I move we continue this discussion at the Village Pump. --[[User:Short Circuit|Short Circuit]] 03:33, 11 October 2008 (UTC)
 
:::I think a better title for Object Serialization might be "Saving/loading program state" and an example that allows many types of language to provide examples. Whilst you might strive for program paradigm neutrality, I still think it would be useful to have tasks that are naturally trivial in some class of languages - say constraints, or bit manipulation.
:::Since we are comparing languages although the task description may describe an algorithm to use, if your language has a feature that is normally used you might be justified in using the built-in feature with an explanation as well as, or instead of, the algorithm asked for. For example, it would be a shame if someone reading the quicksort task went away thinking that it was THE way to sort in Python/Perl/Ruby etc.. --[[User:Paddy3118|Paddy3118]] 16:43, 11 October 2008 (UTC)
Anonymous user