🚀 go-pugleaf

This has been an interesting discussion! and it leads me to ask for some
info if that's OK!


I've got a stem (as I prefer to call them) which holds the index returned
from (not that is matters) a 'SetItem' in VisPro.  It is essentially a
unique 'index' reference.

I grab is thus

indx = VpSetItem Whatever whatever (say adding icons to a container)

The point is that indx would then hold a large unique value, say, 8765321.

I then construct a stem..

data.indx.1 = 'd:\foo\etc\filename.ext'   /* for the sake of this example */
data.indx.2 = 'something else for this example'.



Now, what I find incredibly useful is that I can get to my filename example
by simply refering to


data.8765321.1


Given the large number, 'ck knows what it would take to finally get to
data.87654321.1 to grab the value with conventional arrays.  With rexx's
ability to get straight to the 'element' of the 'array' in one
move...well..I am impressed!

Now, the questions...

(i) Is there a limit as to the 'value' in, say, my example..?  ie: would
    data.99999999.1 suddenly break !?

(ii) What is the largest amount of data I can chuck into a rtexx variable ?
     (I do a historical check on incoming data which I concatenate into
     a massive string variable...  a positive or negative POS(needle, haystack)
     informs me whether the pertinent data is already accounted for.  I am
     just wondering whether there is a final limit as to what can be
     stored in a single variable before I unleash it!)


Rexx stems ain't arrays.  But arrays ain't stems!

Cheers!


Clive
,c.
-- 
------------------------------------------------------------------------
Clive Humble of Artists in Glass, England, Atlantic Ocean (+near+ Europe)
   Desk: chumble@glassnet.com      Home: chumble@agile.glassnet.com
------------------------------------------------------------------------