From ... Path: archiver1.google.com!news1.google.com!newsfeed.stanford.edu!news-spur1.maxwell.syr.edu!news.maxwell.syr.edu!newsfeed.stueberl.de!news.netway.at!nmaster.kpnqwest.net!nnum.kpnqwest.net!EU.net!nreader1.kpnqwest.net.POSTED!not-for-mail Newsgroups: comp.lang.lisp Subject: Re: using dispatch macro characters References: <3D19B3E4.AC474587@eurocom.od.ua> <3234116820393808@naggum.net> Mail-Copies-To: never From: Erik Naggum Message-ID: <3234127962507056@naggum.net> Organization: Naggum Software, Oslo, Norway Lines: 17 User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.2 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 27 Jun 2002 00:52:42 GMT X-Complaints-To: newsmaster@KPNQwest.no X-Trace: nreader1.kpnqwest.net 1025139162 193.71.199.50 (Thu, 27 Jun 2002 02:52:42 MET DST) NNTP-Posting-Date: Thu, 27 Jun 2002 02:52:42 MET DST Xref: archiver1.google.com comp.lang.lisp:35795 * David Golden | Apparently already an IEC standard, draft IEEE and proposed to ISO... Well, the interesting thing about standards is that if you need to do something to which they prescribe a solution, you should do it that way unless you and your partners agree to something else. Standards in a given area should be considered for applicability before anything else, but if they turn out to be nuts, like MOTIS, OSI, ODA, etc, people should have no qualms about leaving them behind to do something better. However, this should not be the first thing you reach for. So I think I shall henceforth have to write these things out more explicitly. -- Guide to non-spammers: If you want to send me a business proposal, please be specific and do not put "business proposal" in the Subject header. If it is urgent, do not use the word "urgent". If you need an immediate answer, give me a reason, do not shout "for your immediate attention". Thank you.