In writing test stubs for the array, directory, and table APIs, I noticed that only array has a HasIndex method. We probably should be consistent between these collection class APIs. However, rather than add HasIndex to directory and table, I suspect removing HasIndex from array is the better course. The AT/GET methods for the collection classes return NULLOBJECT if the item is not in the collection at the given index. This sort of obviates the need for a second HasIndex call since you can distinguish between nothing at that index and .nil stored at that index (unlike what's needed in ooRexx code).
So, given the above, if there are no good arguments advanced for keeping array HasIndex or adding HasIndex for the other types, I'm going to remove the array one. Rick ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ Oorexx-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/oorexx-devel
