interesting array "Feature"?

Hans, Barb, ...
 
I just came across an interesting bug in my code. (see below)  I have a
function which returns a value and assigning that value to an array element.
I had not indexed the array correctly so the function was being "called" for
each element. It was finally failing because not all of the storage for the
array was allocated. I assume, altho I have not tried it, that if the array
would have been fully allocated that all elements would have been assigned a
return value from individual function calls.
 
The question would be: Is this an intended feature and can I expect this
result in the future? 
I'm currently on V5R2M0.
 
 
/Free // This code calls the buildFunctionStruct-Procedure for each
task.FunctionStructure element
 
task.FunctionStructure = buildFunctionStruct(taskName);
 
/End-Free
 
/Free // This is the corrected code which calls the
buildFunctionStruct-Procedure once (my intended result)
 
task.FunctionStructure(x) = buildFunctionStruct(taskName);
 
/End-Free
 
 
Duane
 
 
 



NOTICE: This electronic mail transmission may contain confidential
information and is intended only for the person(s) named.  Any use, copying
or disclosure by any other person is strictly prohibited. If you have
received this transmission in error, please notify the sender via e-mail.