🚀 go-pugleaf

In article <1991Mar5.143615.5847@csc.ti.com> peterson@choctaw.csc.ti.com (Bob Peterson) writes:
|  I see the need for a standard mechanism for accessing a class
|instance's type.  I believe a general mechanism, similar in spirit to
|the property lists found in Lisp, would support not only type
|information, but the needs of other enhanced facilities such as
|programming environments.  I'd like to see the compiler insert into
|each class a static member function that returns a pointer to a singly
|linked list of pointers to a class instance.  The class pointed to
|would have defined only a virtual function returning a descriptor.  The
|descriptor would describe the sort of information the actual instance
|contained, e.g., a description of a type.  Users would be able to
|derive from the language-specified class description expanded classes

....

Seems we're getting hung up arguing details of compiler implementation
rather than issues of language definition.  How should run-time
type information be represented in the language -- as opposed to in the
resulting executable?