home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.lang.lisp.mcl
- Path: sparky!uunet!ftpbox!news.acns.nwu.edu!news.ils.nwu.edu!ils.nwu.edu!forbus
- From: forbus@ils.nwu.edu (Ken Forbus)
- Subject: Porting to MCL: Package problems
- Message-ID: <1993Jan27.195638.11628@ils.nwu.edu>
- Followup-To: comp.lang.lisp.mcl
- Keywords: MCL<> CL?,pain
- Sender: usenet@ils.nwu.edu (Mr. usenet)
- Nntp-Posting-Host: orac.ils.nwu.edu
- Organization: The Institute for the Learning Sciences
- Date: Wed, 27 Jan 1993 19:56:38 GMT
- Lines: 32
-
- I am trying to make some Common Lisp code run under MCL. It runs as is on
- every other Common Lisp I've tried: Lucid and Franz on a variety of machines,
- KCL and AKCL, Symbolics on their own hardware, and even the Symbolics
- CLOE environment under Microsoft Windows. Overall, quite vanilla code.
- Much of it in fact is teaching code, designed to be very
- portable. But it won't run under MCL.
-
- Most of the problems seem to be package related. MCL can't seem to grok
-
- (in-package 'tms)
-
- for instance, and declaring packages in a Symbolics-style attribute line
- appears to make the machine most unhappy.
-
- Presumably others have solved such problems. Is there a file somewhere which
- documents the gotcha's in porting Common Lisp code to MCL? Thanks.
-
- Ken
-
- ==========================================
- Prof. Kenneth D. Forbus
- Qualitative Reasoning Group
- The Institute for the Learning Sciences
- Northwestern University
- 1890 Maple Avenue
- Evanston, Illinois, 60201, USA
-
- email: forbus@ils.nwu.edu
- voice: (708) 491-7699
- fax: (708) 491-5258
- ==========================================
-
-