On 5/25/07, Pardee, Roy <[EMAIL PROTECTED]> wrote:
But it doesn't necessarily follow from that that a class is an object, does it? Not that I mean to argue that .net classes *aren't* objects, mind you--I think probably they are, and the Type class is the class Class. But I'm looking forward to further discussion, as I know there are some nuances of this stuff that I don't understand...
I like to think of it this way. A class is the blueprint for an object and an object is an instance of a class. You have no objects w/o instances; only blueprints for the creation of objects. -- Steve Johnson =================================== This list is hosted by DevelopMentor® http://www.develop.com View archives and manage your subscription(s) at http://discuss.develop.com
