Talk:Loop over multiple arrays simultaneously: Difference between revisions

→‎?: new section
(→‎?: new section)
Line 8:
:For some languages, type declarations just aren't present (either because of type inference or because of the use of value systems which make it unnecessary). More importantly, '''''that's not the point of this task'''''. It's the looping construct that is significant, not the types of the data participating. (Well, assuming that the language can loop over arrays/lists of arbitrary element type; I can't think why anyone would restrict it, but someone somewhere might be silly enough.) –[[User:Dkf|Donal Fellows]] 09:09, 19 November 2009 (UTC)
:: I agree that the point of this task is to highlight the looping construct. My point is that because of the different interpretations of the example task, the differences in the looping mechanisms between languages is, to some extent, obfuscated. I have no problem with the arrays being of different types, I just think it would be better if the solutions were all solving the same task. I certainly wasn't suggesting that type must be explicitly specified by each language <shudder>.--[[User:Tikkanz|Tikkanz]] 20:42, 19 November 2009 (UTC)
 
== ? ==
 
I am removing from the C entry a comment that read:
 
:THIS CANNOT BE RIGHT. PLEASE FIX.
 
The code compiles and runs, and loops over multiple arrays simultaneously, so in that sense, it is right. If anything, it's probably doing too much (there's about 5 times the amount of code this task should need). But I think that that kind of code critique belongs here on the talk page. Alternate versions could go on the main page, if anyone wants to write them. --18:31, 22 July 2011 (UTC)
6,951

edits