Context Navigation

Changes between Version 2 and Version 3 of Ticket #5886, comment 4

v2	v3
29	29	This is where the problem is. If {{{z}}} is {{{1}}} then cols is set to {{{1}}} which means {{{T}}} is a {{{[4,1]}}} array. Trying to access {{{[1,2]}}} should normally cause out of range access error.
30	30
31		The way our simulation code operates right now, if it fails to find a variable in the '''list of simcode''' variables, in this case ~~components[1].T[1,2]~~ for example, it will assume it is a ''temporary variable and tries to generate function like code for it''. You don't have to worry about the details normally. Until you run in to this kinds of odd errors.
	31	The way our simulation code operates right now, if it fails to find a variable in the '''list of simcode''' variables, in this case {{{components[1].T[1,2]}}} for example, it will assume it is a ''temporary variable and tries to generate function like code for it''. You don't have to worry about the details normally. Until you run in to this kinds of odd errors.
32	32
33	33	I understand it would be nice to have better error messages in this case. However this is not something we can fix right now. At least not as a quick fix. For what it is worth I think this error is actually a bit better than having a silent out of bounds access.