Re: Interfaces and Computed Properties

[Norman Palardy <npalardy@great-white-software.com>]

On 26-Nov-08, at 4:10 PM, Lars Jensen wrote:

> > They do not specify HOW to implement something just the API that  
> > will be adhered to
> Well they do specify whether a symbol is implemented as a method or  
> as a property.
They never specify data ... so no properties

Yes this does mean you have to use methods BUT because you can use a  
method getter/setter pair in a manner that is for all intents and  
purposes indistinguishable from a real property I'd use that
ie/ you have no clue if

     myclass.someProperty = 6

is implemented as
   a naked public property
   a getter setter pair with a setter like someProperty(assigns i as  
integer)
   a computed property with a setter


_______________________________________________
Unsubscribe or switch delivery mode:
<http://www.realsoftware.com/support/listmanager/>

Search the archives:
<http://support.realsoftware.com/listarchives/lists.html>