realbasic-nug
[Top] [All Lists]

Re: Instantiating object (Re: New 2K5 trial)

To: REALbasic NUG <realbasic-nug at lists dot realsoftware dot com>
Subject: Re: Instantiating object (Re: New 2K5 trial)
From: Norman Palardy <npalardy at great-white-software dot com>
Date: Tue, 30 Aug 2005 16:14:55 -0600
Delivered-to: realbasic-nug at lists dot realsoftware dot com
References: <E66B2B85-5858-45C4-A338-42CDFF8ABC3D at innernine dot com> <6f5cb228778072c5534ad8c81ffeebdd at satx dot rr dot com> <537B9BB5-CC90-4FC7-AD2A-2E6AD8F4A541 at innernine dot com> <bbe003f594749364dcbad65d97ab3cd4 at satx dot rr dot com> <a0620071cbf3a86fffc5a at [10 dot 0 dot 1 dot 4]>

On Aug 30, 2005, at 3:59 PM, Joseph J. Strout wrote:

At 4:36 PM -0500 8/30/05, William Squires wrote:

I'm not saying to 'New' a reference to "Object", as you can't - it's an abstract class; intended only to be subclassed. You 'New' a reference to some other subclass (that's not abstract), then assign the reference thereof to a variable (or array) of type 'reference-to-Object' so that you can take advantage of polymorphism without type-mismatch errors.

This thread is about actually, literally, saying "New Object". Apparently that generates an error in REALbasic 2005, though it was allowed in 5.5.

Yes, but 55 did allow other things that probably should have been flagged as errors of one kind or another Maybe this is just one of those "should have been an error in 5.5 but wasn't caught but now is" kinds of things ?

What would you DO with one created this way anyways ?


_______________________________________________
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>