From ... Path: archiver1.google.com!news1.google.com!newsfeed.stanford.edu!newsfeeds.belnet.be!news.belnet.be!news2.kpn.net!news.kpn.net!nslave.kpnqwest.net!nloc.kpnqwest.net!nmaster.kpnqwest.net!nreader2.kpnqwest.net.POSTED!not-for-mail Newsgroups: comp.lang.lisp Subject: Re: Preventing a class from being instantiated References: <9u4802$66q$1@news3.cadvision.com> <873d2yi5fq.fsf@orion.bln.pmsf.de> <3C087470.C1EA3DD2@nyc.rr.com> Mail-Copies-To: never From: Erik Naggum Message-ID: <3216203139877076@naggum.net> Organization: Naggum Software, Oslo, Norway Lines: 18 User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.1 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 01 Dec 2001 13:45:41 GMT X-Complaints-To: newsmaster@KPNQwest.no X-Trace: nreader2.kpnqwest.net 1007214341 193.71.66.49 (Sat, 01 Dec 2001 14:45:41 MET) NNTP-Posting-Date: Sat, 01 Dec 2001 14:45:41 MET Xref: archiver1.google.com comp.lang.lisp:21634 * Kenny Tilton | I suggest that any abstract class be named: @class-name@ Please do not use up a very useful macro character like that. This is almost as bad as suggesting that people actually _use_ $ as the first position in symbol names -- it is such an obvious thing to want to use for non-constituent macro purposes. % is always available as a normal constituent character and is frequently used to mar "internal" symbols, which to me seems what an abstract class is, but I do _not_ see the need for syntactic suger-coating of symbol names just to keep losers from instantiating an abstract class. /// -- THE past is not more important than the future, despite what your culture has taught you. Your future observations, conclusions, and beliefs are more important to you than those in your past ever will be. The world is changing so fast the balance between the past and the future has shifted.