| To: | REALbasic Network Users Group <realbasic-nug at lists dot realsoftware dot com> |
|---|---|
| Subject: | Re: Constructors for Modules |
| From: | Will Leshner <leshner at ljug dot com> |
| Date: | Wed, 30 Jul 2003 12:33:15 -0700 |
Yes. I completely agree. I would also like to be able to enforce
Singleton behavior. It *might* be possible to do this ourselves if we
could indicate that a constructor was private (this would be a new
feature, not the current "protected"). I think we might also need class
methods. I believe if we had those two things we might be able to
guarantee Singleton-ness ourselves. And they would be great features to
have anyway.
Thomas Reed wrote: The one aspect of this that I *can* see wanting support for is singletons. It would be nice if there were some way of enforcing singleton behavior for a class. (ie, prevent more than one from being created) --- A searchable archive of this list is available at: <http://support.realsoftware.com/listarchives/search.php> Unsubscribe or switch delivery mode: <http://support.realsoftware.com/listmanager/> . |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: CoreMIDI, Joseph J. Strout |
|---|---|
| Next by Date: | Re: CoreMIDI, Eden |
| Previous by Thread: | Re: Constructors for Modules, Thomas Reed |
| Next by Thread: | Re: Constructors for Modules, Walter Purvis |
| Indexes: | [Date] [Thread] [Top] [All Lists] |