Talk:Compare a list of strings: Difference between revisions

→‎Planned task changes: Yep. With caveat...
(Planned task changes -- input from admins/mods needed)
 
(→‎Planned task changes: Yep. With caveat...)
Line 53:
''<u>Rationale:</u>''
 
Most Rosetta Code tasks encourage implementorsimplementers to show their solutions in the form of a complete, ready-to-run program that also demonstrates the functionality using a few test cases. And for most tasks that makes sense.
 
But in this task, the "demonstration code" (properly initializing the program, populating the arrays, looping over test cases, calling the tests, printing the output, properly terminating the program) would in most languages be larger and more attention-grabbing than the code for doing the tests themselves and effectively "drown it out". Such a poor signal-to-noise ratio makes it much more difficult to compare the solutions from different languages - which, for a conceptually simple task like this, should be easy. Not to mention it makes it difficult to know which imported libraries are needed for the actual test, and which for the demo code.
Line 65:
 
Cheers, --[[User:Smls|Smls]] ([[User talk:Smls|talk]]) 15:16, 1 July 2014 (UTC)
 
:Hi Smls, I don't think this should be for administrators as much as it should be for non-newbies. As a non-newbie I should point out that although draft, the twelve implementations makes it more difficult to make a change and get everyone to update. Against that though, it has only been a day so the implementors should still be "around".
:I am inclined to think that if you really want to make the change and that change will invalidate some entries, then you could do it but also add:
::<nowiki>{{incorrect|TheLanguage|The reason.}}</nowiki>
:tags to all the entries that need updating so people are more likely to find out that their particular languages implementation needs changing.
: That's one opinion :-)
:--[[User:Paddy3118|Paddy3118]] ([[User talk:Paddy3118|talk]]) 16:56, 1 July 2014 (UTC)
Anonymous user