From ... From: Erik Naggum Subject: Re: Allegro compilation warnings Date: 2000/10/16 Message-ID: <3180723380733118@naggum.net>#1/1 X-Deja-AN: 682259540 References: <3180376670416509@naggum.net> <3180475124104589@naggum.net> mail-copies-to: never Content-Type: text/plain; charset=us-ascii X-Complaints-To: newsmaster@eunet.no X-Trace: oslo-nntp.eunet.no 971738675 15787 195.0.192.66 (16 Oct 2000 23:24:35 GMT) Organization: Naggum Software; vox: +47 800 35477; gsm: +47 93 256 360; fax: +47 93 270 868; http://naggum.no; http://naggum.net User-Agent: Gnus/5.0803 (Gnus v5.8.3) Emacs/20.7 Mime-Version: 1.0 NNTP-Posting-Date: 16 Oct 2000 23:24:35 GMT Newsgroups: comp.lang.lisp * Paolo Amoroso | MK-DEFSYSTEM comes with good documentation. Would that be a good | starting point for creating a standard? What kind of work would it | take to turn that documentation into a useful standard? Some sort of agreement on (A) what the language implemented by the system is (a specification), (B) what the language implemented by the system is not (a scope), (C) what constitues local enhancements and additions as opposed to basic features (a conformance clause). Then we would have a good starting point. That we already have one implementation is not in and by itself a negative. That we have _only_ one, is. A specifcation must be sufficiently precise to allow multiple implementations, even with multiple sets of local enhancements and local features. I think we need a standard defsystem. I don't think we should use existing code for that job just because it's there. Therefore, the questions you ask are very pertinent to the development of a real standard and real formal agreement. #:Erik -- I agree with everything you say, but I would attack to death your right to say it. -- Tom Stoppard