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. My plugin is accessing some directory services (proprietary, but conceptually similar to LDAP).
From some lookup function, I need to return the results, which is basically a two-dimensional array. each row is one matching record, with the columns determined by the fields requested.
Both dimensions would be unknown, and would seem to encounter the same problem inside a class as outside.
Steve Cochran _______________________________________________ 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>
