| To: | REALbasic NUG <realbasic-nug@lists.realsoftware.com> |
|---|---|
| Subject: | Interfaces and Computed Properties |
| From: | Michael Diehr <md03@xochi.com> |
| Date: | Wed, 26 Nov 2008 12:17:34 -0800 |
| 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 |
| Reply-to: | REALbasic NUG <realbasic-nug@lists.realsoftware.com> |
| Sender: | realbasic-nug-bounces@lists.realsoftware.com |
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?
it would be nice to be able to say Interface XYZ method Load method Save property X as integer and then have classWhichImplementsXYZ: sub Load sub Save X as integer ? _______________________________________________ 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> |
|---|---|---|
| ||
| Previous by Date: | [ANN] SEEdit Maxi with Sparkle Tool, Sven E Olsson |
|---|---|
| Next by Date: | Re: Interfaces and Computed Properties, Charles Yeomans |
| Previous by Thread: | [ANN] SEEdit Maxi with Sparkle Tool, Sven E Olsson |
| Next by Thread: | Re: Interfaces and Computed Properties, Charles Yeomans |
| Indexes: | [Date] [Thread] [Top] [All Lists] |