Anonymous user
Talk:Odd word problem: Difference between revisions
→Explanations: more about intent, curiosities, doc, and a task suggestion
(→Explanations: more about intent, curiosities, doc, and a task suggestion) |
|||
Line 14:
:::: I don't know how to better describe it other than "making order of executation flexible." Maybe it's best to infer it by examples, just take a look at the <code>defer</code> in second Go example and coroutines in the TCL one. --[[User:Ledrug|Ledrug]] 18:46, 4 November 2011 (UTC)
::::: I really do not know what you mean by "making order of execution flexible" -- it seems to me that you are doing exactly the opposite? Moreover, you earlier stated that you are explicitly trying to make the problem difficult -- but that strikes me as the essence of bad design? Anyways, I am not seeing the point or the gist, here. --[[User:Rdm|Rdm]] 22:03, 4 November 2011 (UTC)
:::::: I understand your frustration. I don't know enough APL or J to even begin but I do know that there is a different way of looking at things. We saw it with the Longest String Puzzle/Challenge as well. I still think the task is under (or incorrectly specified) with respect to intent. I now thing that puzzles/challenges of this type are really properly categorized as 'curiosities'. So if I were to paraphrase, the basic problem is clear but the restrictions muddy the waters (also familiar). The 'read' method is given as unbuffered and destructive hence the no peeking, putting back, etc. The curiosity/challenge is in finding a way to reverse through program control alone without intermediate buffers. This works for most languages but I confess that I very quickly hit a wall when I try and think about this in APL or J. --[[User:Dgamey|Dgamey]] 02:41, 5 November 2011 (UTC)
:::::: One thing that I think is missing in curiosities of this type is documentation about what we coded. It's one thing to have a very specific and comparable task as comparisons can be more easily made. But when there is more variation and style it becomes harder to compare and see how things work. BTW. As I was trying to read the TCL, I'd love to see a tightly prescribed task for simple co-routine transfers.
== Other References ==
| |||