Talk:Longest string challenge: Difference between revisions
Content added Content deleted
(→Restrictions: restrictions were core of intent) |
|||
| Line 52: | Line 52: | ||
I had to chuckle at the comment on the C submission as I think it proves the point quite well. Clearly, I need to document the point better :) |
I had to chuckle at the comment on the C submission as I think it proves the point quite well. Clearly, I need to document the point better :) |
||
: While I think about how to word it, let me explain. This site allows people to compare implementations in different languages. Restrictions force people to find other ways. To choose the road less traveled. Now this may require a technique that would be useful in some other problem but perhaps overkill in the simple unrestricted case. This can show people different techniques. The C contribution's cmp procedure is a case in point (I think). My C is very rusty (entirely seized up) and it doesn't look like a cheat to me. But I only have an inkling of how it may work. I'd have to crack my old copy of K&R and scratch my head a bit for it to be clear. A fluent C programmer would 't need to, but on the other hand they wouldn't be on this site to read code. Where I failed in the task description is to require people to provide some description of how they got around the restriction so that people coming from other languages will be able to understand. I'll add this to the task description. --[[User:Dgamey|Dgamey]] 13:01, 13 August 2011 (UTC) |
: While I think about how to word it, let me explain. This site allows people to compare implementations in different languages. Restrictions force people to find other ways. To choose the road less traveled. Now this may require a technique that would be useful in some other problem but perhaps overkill in the simple unrestricted case. This can show people different techniques. The C contribution's cmp procedure is a case in point (I think). My C is very rusty (entirely seized up) and it doesn't look like a cheat to me. But I only have an inkling of how it may work. I'd have to crack my old copy of K&R and scratch my head a bit for it to be clear. A fluent C programmer would 't need to, but on the other hand they wouldn't be on this site to read code. Where I failed in the task description is to require people to provide some description of how they got around the restriction so that people coming from other languages will be able to understand. I'll add this to the task description. --[[User:Dgamey|Dgamey]] 13:01, 13 August 2011 (UTC) |
||
==Icon uses boolean datatypes== |
|||
'move(1)' must return something coerced to a boolean for the if statement/expression to work on its return value. In fact, their are more conditionals, so things are getting coerced to booleans there too. I think the problem statement could prove tough to tie down ;-) <br> --[[User:Paddy3118|Paddy3118]] |
|||