The oopy way to do this (where the array in question is a property of another object) is to have the method code that operates on the array in the other object as well. Since it's a property of that other object, the other object should be smart enough to know how its own array needs to be manipulated. The object that requires the manipulation needn't even know that it's an array. This makes it far easier and requires fewer domino-ing changes when, for instance, you need to change over to a table driven solution and dump the array altogether.
On Mon, Apr 23, 2012 at 5:09 PM, Michael Savage <[email protected]> wrote: > Is there a way? > > TIA, > Mike > [excessive quoting removed by server] _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://leafe.com/mailman/listinfo/profox OT-free version of this list: http://leafe.com/mailman/listinfo/profoxtech Searchable Archive: http://leafe.com/archives/search/profox This message: http://leafe.com/archives/byMID/profox/CAFuU78cm9C_XAHNA2oxUcVOD8=gagscb_csvsbukqnozztx...@mail.gmail.com ** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.
