| To: | REALbasic Plugins <realbasic-plugins at lists dot realsoftware dot com> |
|---|---|
| Subject: | Re: Operator_Convert |
| From: | Mars Saxman <mars at realsoftware dot com> |
| Date: | Tue, 28 Jun 2005 19:41:28 -0700 |
| Delivered-to: | realbasic-plugins at lists dot realsoftware dot com |
| References: | <5ffd0bf43fa05305274a0fdda756ca70 at mac dot com> <2AD239D0-509F-439C-927F-442C7A45482E at realsoftware dot com> <80f5afc541e26f6b67cd9f6a450ec95e at mac dot com> |
On Jun 28, 2005, at 7:30 PM, Alfred Van Hoek wrote: Consider the following situation: Class myClass: Operator_Convert(control as myControl) Control myControl: Operator_Convert() as myClass dim a as myClass dim b as myControl a = bwill not call the initializer of myClass, unless Operator_Convert() as myClass is removed. This is intended behavior? Yes. If both conversions exist, the "convert to" operator always takes precedence over the "convert from" operator. Mars Saxman REAL Software _______________________________________________ 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> |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: Operator_Convert, Alfred Van Hoek |
|---|---|
| Next by Date: | Operator_Convert To, Alfred Van Hoek |
| Previous by Thread: | Re: Operator_Convert, Alfred Van Hoek |
| Next by Thread: | hidden classes, Will Leshner |
| Indexes: | [Date] [Thread] [Top] [All Lists] |