we have accessor functions now to emulate properties-  via computed
properties.  This is great for making getter/setter methods behave as
properties.  What would be even more useful would be to be able to create
similar accessor methods ( for encapsulation versatility etc ) that behave
to the outside world as ARRAYS.

One major benefit of this would be to be able to use the FOR EACH construct
on these methods.  That would give us the control and versatility of using
methods and our own code to govern access to lists, arrays etc.  while still
retaining the power and readability of using FOR EACH as oppoosed to indexes
and ubound type calls.

I guess some of this might be achievable with new operator overload methods.

Note that C#  already has some features like this - ie to make a class
behave as an array to the outside world.


Any opinions chaps  ( and chapesses )

Dan Stenning

WWW.13flatFIVE.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>

Reply via email to