Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.1 6/24/83; site arizona.UUCP
Path: utzoo!watmath!clyde!burl!ulysses!mhuxl!ihnp4!arizona!rogerh
From: rogerh@arizona.UUCP (Roger Hayes)
Newsgroups: net.lang.st80
Subject: Re: How to 'classify' objects
Message-ID: <15464@arizona.UUCP>
Date: Thu, 13-Sep-84 18:24:54 EDT
Article-I.D.: arizona.15464
Posted: Thu Sep 13 18:24:54 1984
Date-Received: Tue, 25-Sep-84 01:21:27 EDT
References: <1765@uw-june>
Organization: Dept of CS, U of Arizona, Tucson
Lines: 25

Why not use (a series of) respondsTo: messages?

Do you intend to set up a completely separate "classification" scheme, 
separate from the behavior of an object?  What meaning would such a
"classification" have?  I must not understand.

If you need to create objects which are distinguishable, you can put
isAFunnyThing methods in their protocols; then the test is
	(object) respondsTo: #isAFunnyThing.
eg, to create FunnyThing integers,

classname	FunnyInteger
superclass	Integer
instance methods	[
	isAFunnyThing
		^ true
]

	Roger Hayes
	University of Arizona
	{ihnp4,ucbvax}!arizona!rogerh.UUCP
	rogerh@Arizona.CSNET