wedekind@arisia.Xerox.COM (Jerry Wedekind) (03/11/89)
Can anyone supply or point me to a description of the "right" way to make one's class a bona fide OOPS class, i.e. one able to support OOPS i/o, isA(), isKindOf(), and otherwise be a full-fledged member of the OOPS class hierarchy? So far I have been taking my cues from Keith Gorlen's '87 USENIX article and the OOPS sources, but I suspect that I am overlooking some fine points. thank you Jerry ARPA: Wedekind.ElSegundo@Xerox.com UUCP: wedekind@arisia.uucp