From ... Path: archiver1.google.com!news1.google.com!newsfeed.stanford.edu!news-spur1.maxwell.syr.edu!news.maxwell.syr.edu!newsfeed.icl.net!newsfeed.fjserv.net!news.teledanmark.no!uninett.no!uio.no!nntp.uio.no!ifi.uio.no!not-for-mail From: Erik Naggum Newsgroups: comp.lang.lisp Subject: Re: Legal ANSI comment form? Date: 24 Aug 2002 20:58:12 +0000 Organization: Naggum Software, Oslo, Norway Lines: 20 Message-ID: <3239211492160492@naggum.no> References: <3D655868.BFE4C243@cs.cmu.edu> <4k7miv7mn.fsf@beta.franz.com> <4elcpk2jp.fsf@beta.franz.com> <3239153188775738@naggum.no> <4fzx4mbkj.fsf@beta.franz.com> <3D67DABD.AE79E086@dls.net> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Trace: maud.ifi.uio.no 1030222693 13273 129.240.64.16 (24 Aug 2002 20:58:13 GMT) X-Complaints-To: abuse@ifi.uio.no NNTP-Posting-Date: 24 Aug 2002 20:58:13 GMT Mail-Copies-To: never User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.2 Xref: archiver1.google.com comp.lang.lisp:38692 * "Paul F. Dietz" | Somehow one should be able to use this idiom: | | #+#.(predicate-evaluating-to-a-feature-expression) ... | | instead of having to preload attributes of the system as symbols pushed onto | the *feature* list. A useful extension to the feature scheme would be to treat any form whose car was not the defined `and´, `or´ and `not´ as a macro to be expanded. That way, a feature expression could evaluate to (or) or (and) transparently if the macro returned just `nil´ or `t´, too, hiding what appears to trigger some irrational aesthetics factor that considers #+ignore OK even though it totally confuses the semantic spaces of feature names and natural languages. -- Erik Naggum, Oslo, Norway Act from reason, and failure makes you rethink and study harder. Act from faith, and failure makes you blame someone and push harder.