From: Bob R. <ro...@rg...> - 2002-03-19 19:22:33
|
I recently started using the excl:*fasl-default-type* feature of Allegro Common Lisp, which lead me to notice that defsystem ignores it. To fix this, one can change the line that reads #+excl ("cl" . "fasl") (line 501, interestingly) to something like #+excl ("cl" . ,excl:*fasl-default-type*) I notice similar changes have been made for CMUCL and LispWorks. It is also possible to delete this line altogether so that the catch-all case at the bottom kicks in: ("lisp" . ,(pathname-type (compile-file-pathname "foo.lisp"))) The Allegro compile-file-pathname implementation uses excl:*fasl-default-type*, so this has the same effect for the fasl type, but winds up changing the nominal preferred Lisp source file type incompatibly to "lisp" (which is my personal preference, though). Hope this is useful, -- Bob Rogers ESS Technology, Inc. http://rgrjr.dyndns.org/icancad/ |
From: Marco A. <ma...@cs...> - 2002-03-22 18:55:17
|
Thanks. Good catch. I think I will actually change the line as #+excl ("cl" . ,(pathname-type (compile-file-pathname "foo.cl") )) In order to retain the treatment of the special "cl" extension. Cheers -- Marco Antoniotti ======================================================== NYU Courant Bioinformatics Group tel. +1 - 212 - 998 3488 719 Broadway 12th Floor fax +1 - 212 - 995 4122 New York, NY 10003, USA http://bioinformatics.cat.nyu.edu "Hello New York! We'll do what we can!" Bill Murray in `Ghostbusters'. |
From: Bob R. <ro...@rg...> - 2002-03-22 19:13:50
|
From: Marco Antoniotti <ma...@cs...> Date: Fri, 22 Mar 2002 13:55:14 -0500 Thanks. Good catch. I think I will actually change the line as #+excl ("cl" . ,(pathname-type (compile-file-pathname "foo.cl") )) In order to retain the treatment of the special "cl" extension. That does seem like the best thing for backward compatibility. (Though, does defsystem do much with the source file type? Even with the original default, it had no trouble realizing that it needed to compile my *.lisp files. Would anything break for ".cl" files if ".lisp" were used? Just curious, though it seems better to prefer "vendor-independent" file types (IMHO) as long as the vendor-specific ones also work.) Thanks, -- Bob |
From: Marco A. <ma...@cs...> - 2002-03-25 15:23:25
|
> From: Bob Rogers <ro...@rg...> > Content-Type: text/plain; charset=us-ascii > CC: clo...@li... > Sender: clo...@li... > X-BeenThere: clo...@li... > X-Mailman-Version: 2.0.5 > Precedence: bulk > List-Help: <mailto:clo...@li...?subject=help> > List-Post: <mailto:clo...@li...> > List-Subscribe: <https://lists.sourceforge.net/lists/listinfo/clocc-list>, > <mailto:clo...@li...?subject=subscribe> > List-Id: <clocc-list.lists.sourceforge.net> > List-Unsubscribe: <https://lists.sourceforge.net/lists/listinfo/clocc-list>, > <mailto:clo...@li...?subject=unsubscribe> > List-Archive: <http://www.geocrawler.com/redir-sf.php3?list=clocc-list> > X-Original-Date: Fri, 22 Mar 2002 14:13:47 -0500 > Date: Fri, 22 Mar 2002 14:13:47 -0500 > Content-Length: 911 > > From: Marco Antoniotti <ma...@cs...> > Date: Fri, 22 Mar 2002 13:55:14 -0500 > > Thanks. Good catch. I think I will actually change the line as > > #+excl ("cl" . ,(pathname-type (compile-file-pathname "foo.cl") )) > > In order to retain the treatment of the special "cl" extension. > > That does seem like the best thing for backward compatibility. > > (Though, does defsystem do much with the source file type? Even with > the original default, it had no trouble realizing that it needed to > compile my *.lisp files. Would anything break for ".cl" files if > ".lisp" were used? Just curious, though it seems better to prefer > "vendor-independent" file types (IMHO) as long as the vendor-specific > ones also work.) The source file extension is under programmer control. It is the default that somehow needs to be hardwired somewhere. Having "cl" as the extension for ACL seems to be what Franz expects. Other than that, I have no problems with defaulting to "lisp". Cheers -- Marco Antoniotti ======================================================== NYU Courant Bioinformatics Group tel. +1 - 212 - 998 3488 719 Broadway 12th Floor fax +1 - 212 - 995 4122 New York, NY 10003, USA http://bioinformatics.cat.nyu.edu "Hello New York! We'll do what we can!" Bill Murray in `Ghostbusters'. |
From: Bob R. <ro...@rg...> - 2002-03-25 15:43:01
|
From: Marco Antoniotti <ma...@cs...> Date: Mon, 25 Mar 2002 10:23:21 -0500 > From: Bob Rogers <ro...@rg...> > Date: Fri, 22 Mar 2002 14:13:47 -0500 > > From: Marco Antoniotti <ma...@cs...> > Date: Fri, 22 Mar 2002 13:55:14 -0500 > > Thanks. Good catch. I think I will actually change the line as > > #+excl ("cl" . ,(pathname-type (compile-file-pathname "foo.cl") )) > > In order to retain the treatment of the special "cl" extension. > > That does seem like the best thing for backward compatibility. > > (Though, does defsystem do much with the source file type? Even with > the original default, it had no trouble realizing that it needed to > compile my *.lisp files. Would anything break for ".cl" files if > ".lisp" were used? Just curious, though it seems better to prefer > "vendor-independent" file types (IMHO) as long as the vendor-specific > ones also work.) The source file extension is under programmer control. It is the default that somehow needs to be hardwired somewhere. Having "cl" as the extension for ACL seems to be what Franz expects . . . Good point. In fact, I only just noticed that I had been specifying: :source-extension "lisp" in my defsystem forms (which, of course, is why it's been using ".lisp" all along). So the default really doesn't matter to me, and you have persuaded me that ".cl" is the best default for ACL. (I probably should have been able to figure this out on my own . . . ) Thanks for bearing with me, -- Bob Rogers |