OK to pass big data in 'the result'?

[Stephen Barncard]

I don't think it's any different than returning from a 
function..although I haven't done it this way much. I'm not sure if 
you can pass arrays this way for instance but that could just be 
converted into a return-delimited table.

This would be useful for a custom Answer or Ask dialog that would 
work the same way with the same params.


>Is anyone aware of any drawbacks in using 'the result' as a 
>container for passing, say, a bunch of records from one handler to 
>another? Like this:
>
>
>on processRecords
>   getRecords
>   put the result into tRecordList
>   repeat for each line tLine in it
>     -- your code here
>   end repeat
>end processRecords
>
>
>on getRecords
>   put the uBigList of stack "XYZ" into tList
>   delete stack "XYZ" -- to remove it from memory
>   return tList
>end getRecords
>
>
>Any drawbacks? Speed or memory or other issues?
>
>I realize there are clearer, cleaner ways to do this... in a new dev 
>(read "perfect") world at least. But I'm not in that world at the 
>moment.
>
>Thanks -
>Phil Davis

-- 


stephen barncard
s a n  f r a n c i s c o
- - -  - - - - - - - - -