Talk:Teacup rim text: Difference between revisions

Content added Content deleted

Inline

Revision as of 12:06, 5 August 2019 (view source) Hout (talk \| contribs) (→‎A good task description specifies a problem rather than a procedure) ← Older edit		Revision as of 12:11, 5 August 2019 (view source) Hout (talk \| contribs) (→‎百花齐放) Newer edit →
Line 16:		Line 16:
	(Not all languages or techniques of code composition are built around a notion of 'procedure'. In the traditions (and even architectures) of Lisp, Scheme, Racket, Prolog, ML, Haskell etc, the process of '''evaluation''' is central).		(Not all languages or techniques of code composition are built around a notion of 'procedure'. In the traditions (and even architectures) of Lisp, Scheme, Racket, Prolog, 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)		More productive, in the Rosetta Code context, to just state the problem, leave the technique of its solution to the contributors, and let a hundred flowers bloom. [[User:Hout\|Hout]] ([[User talk:Hout\|talk]]) 12:04, 5 August 2019 (UTC)