Talk:MD5: Difference between revisions
Guidelines.
(pseudocode note) |
(Guidelines.) |
||
Line 7:
:This really should be a task to encode the algorithm. There are other tasks that demonstrate calling functions and external routines. I thing the original task description intended this, unfortunately they didn't say it clearly. I really do think all of the tasks not in the spirit should be marked as needing improvement if not as outright incorrect. However, since they've been allowed to sit for so long marking for improvement is probably enough. --[[User:Dgamey|Dgamey]] 03:33, 28 September 2010 (UTC)
:If an implementation of the task uses a native library then the code should be included here or excerpted (rather than just an offsite link as has been observed before) --[[User:Dgamey|Dgamey]] 04:00, 28 September 2010 (UTC)
::The task was created before we had a policy on use of external libraries. (Heck, it's three years old; it's ''going'' to be crufty.) What I tell people, now, is that if a programmer in a language would use an external library to solve a problem, then that's just fine; if use of a language involves using libraries, than that's ''de facto'' idiomatic for that language. If they wouldn't, that's also fine. Side-by-side examples comparing native and library solutions are fine, too; what isn't done in a library demonstrates native constructs. If we really want to see implementations of MD5 hashing, create a task specific to implementing it. (Actually, that might even bee a good opportunity to try the new [[Rosetta Code:Add a Task]] guideline page.) --[[User:Short Circuit|Michael Mol]] 10:53, 28 September 2010 (UTC)
==Shouldn't this be...==
| |||