On 25-Jan-07, at 3:39 PM, Stephen A. Cochran Lists wrote:
On Jan 25, 2007, at 11:41 AM, [EMAIL PROTECTED] wrote:
I think the generally preferred idiom is to make your own container
class and accessor specific to your data. For example, see Group2D,
which is essentially a wrapper for an array of Object2Ds (plus some
additional functionality).
I thought about that, but it seems a class would run into the same
issues.
For public plugins I'll tend to use wrapper classes, but for in-house
stuff I'll often return a delimited string or memoryblock from the
plugin and use a helper method in RB that creates and returns an array.
Frank.
<http://developer.chaoticbox.com/>
_______________________________________________
Unsubscribe or switch delivery mode:
<http://www.realsoftware.com/support/listmanager/>
Search the archives of this list here:
<http://support.realsoftware.com/listarchives/lists.html>
