Talk:Assigning Values to an Array: Difference between revisions
Talk:Assigning Values to an Array (view source)
Revision as of 23:11, 12 October 2008
, 15 years agoClarification
(Clarification) |
|||
| (2 intermediate revisions by 2 users not shown) | |||
Line 4:
: Seconded: am I supposed to assign a value to an array or write a function/routine/procedure to assign a value to an array? [[User:Sgeier|Sgeier]] 01:09, 20 February 2007 (EST)
::I think the task is more complicated than need be. In fact, it should probably be broken into an "Assigning values" and a "Checking to see if a value exists" task. --[[User:Short Circuit|Short Circuit]] 08:04, 20 February 2007 (EST)
::I'm not sure what I was thinking. (^) "Assigning values to an array" should be a separate task from "create a function to do X". --[[User:Short Circuit|Short Circuit]] 23:11, 12 October 2008 (UTC)
== Type of error to return? Type of index? ==
Line 15:
::A more fair task formulation would be to instruct the programmer to catch the errors before the OS or the PL, so that neither OS nor the inbuilt, should need to detect any error. [[User:Rursus|Rursus]] 07:19, 31 December 2007 (MST)
:::I think it might be appropriate, despite the amount of code already in the task, to split the task between Assigning Values to an Array, and one for catching errors. The problem is, what kinds of errors need to be caught? Not all languages recognize array bounds, for example. As it is, error checking distracts from what would typically be a syntactical problem, not a procedural problem. Thoughts? --[[User:Short Circuit|Short Circuit]] 22:43, 5 January 2008 (MST)
::BTW, i rewrote the [[array]] article, because it only described the compmetrics, and the numeric access, not the lower and upper bounds, nor the everything-inbetween-can-be-accessed rule. [[User:Rursus|Rursus]] 07:25, 31 December 2007 (MST)
| |||