Talk:Teacup rim text: Difference between revisions
→A good task description specifies a problem rather than a procedure
No edit summary |
|||
Line 7:
:: Okay that's done. How do I tell the Perl6 contributor to abbreviate his output? [[User:Axtens|Axtens]] ([[User talk:Axtens|talk]]) 03:40, 5 August 2019 (UTC)
==A good task description specifies a problem rather than a procedure==
The real task/problem here is to identify and display a subset of words (in a given lexicon) that are 'circular' in the sense which you describe.
The current formulation (para 3) is the narration of a '''procedure''', rather than the statement of a problem or task, and is perhaps not yet quite consistent with the Rosetta Code goal (see the landing page) of aiding ''a person with a grounding in one approach to a problem in learning another''.
(Not all languages or techniques of code composition are built around a notion of 'procedure'. In the traditions of Lisp, Scheme, Racket, ML, Haskell etc, the process of '''evaluation''' is central).
Usually better to just state the problem, and leave the technique of its solution to the contributors. [[User:Hout|Hout]] ([[User talk:Hout|talk]]) 12:04, 5 August 2019 (UTC)
| |||