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: Stefan Pantke <seaside dot ki at mac dot com>
Date: Mon, 29 Aug 2005 21:21:02 +0200
Delivered-to: realbasic-nug at lists dot realsoftware dot com
References: <E66B2B85-5858-45C4-A338-42CDFF8ABC3D at innernine dot com>

Am 29.08.2005 um 20:16 schrieb Juergen Schreck:

On Aug 29, 2005, at 9:24 AM, Joseph J. Strout wrote:

- This doesn't compile:

        Dim a As New Object , b As New Object

  Neither compiles this

    Dim a, b As New Object

I see a bug icon, but no explanation. Do we have a new syntax here?

I'm not sure what's going on there.

The bug explanation in r2 is: 'There is no class with this name' .

The LR sez:

"Object is the base class of all other classes. Any object can be assigned into a variable of type Object. The default value of a new instance of an object is Nil. The Object class has no properties, methods, or events."

So I'd say since the default instance has a value of NIL and you can't instantiate NIL, you therefore can't instantiate Object.

Hm? I can't believe that is is the reason. If any object is based on
the object class and I can create instances of all classes, then object
should be able to instantiate too.

But, well, this tends to get academic...


I'm curious as to why someone would want to create and object instance anyway?

Don't ask me! I simply can't remember why this code was port of
the project.

I now even used the two variable with this ugly names...

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