realbasic-nug
[Top] [All Lists]

Re: Interfaces and Computed Properties

To: REALbasic NUG <realbasic-nug@lists.realsoftware.com>
Subject: Re: Interfaces and Computed Properties
From: Norman Palardy <npalardy@great-white-software.com>
Date: Wed, 26 Nov 2008 13:47:57 -0700
Authentication-results: mx.google.com; spf=neutral (google.com: 74.124.194.228 is neither permitted nor denied by best guess record for domain of realbasic-nug-bounces@lists.realsoftware.com) smtp.mail=realbasic-nug-bounces@lists.realsoftware.com
Delivered-to: listarchive@realsoftware.com
In-reply-to: <4F4D1ADF-52CE-4EBA-9346-9BE37992CCDD@xochi.com>
References: <4F4D1ADF-52CE-4EBA-9346-9BE37992CCDD@xochi.com>
Reply-to: REALbasic NUG <realbasic-nug@lists.realsoftware.com>
Sender: realbasic-nug-bounces@lists.realsoftware.com

On 26-Nov-08, at 1:17 PM, Michael Diehr wrote:

Let's say you have an interface, and one of the items in it is really a property. It seems that a class implementing the interface can't have a property with the same name as the interface method (this makes sense, I think). However I'm wondering if there's a clean way to accomplish this using computed properties, or 'assigns' or similar? To rephrase my question -- can Interfaces only describe Methods, or can they describe Properties as well?

Methods only
They do not specify HOW to implement something just the API that will be adhered to
A property of any kind is an implementation detail

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

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


<Prev in Thread] Current Thread [Next in Thread>