From ... From: Erik Naggum Subject: Re: Building a "loadable" tar file. Date: 2000/03/23 Message-ID: <3162824624300417@naggum.no>#1/1 X-Deja-AN: 601393880 References: <38D8E85F.2F16104C@beta.csd.anglia.ac.uk> <38D9EE02.EE5ED48C@iname.com> <38DA068E.DE75118D@pindar.com> <38DA395B.896D1326@pindar.com> mail-copies-to: never Content-Type: text/plain; charset=us-ascii X-Complaints-To: newsmaster@eunet.no X-Trace: oslo-nntp.eunet.no 953835827 19315 195.0.192.66 (23 Mar 2000 18:23:47 GMT) Organization: Naggum Software; vox: +47 8800 8879; fax: +47 8800 8601; http://www.naggum.no User-Agent: Gnus/5.0803 (Gnus v5.8.3) Emacs/20.5 Mime-Version: 1.0 NNTP-Posting-Date: 23 Mar 2000 18:23:47 GMT Newsgroups: comp.lang.lisp * Marco Antoniotti | 1 - Yes. I'd like LOAD to recognize a file which was the result of a | collection operation of many fasl files, and "do the right" thing | with it. | | 2 - This would require a change in the standard. huh? why is this? | 3 - Some CL implementations allow you to actually 'cat' fasl files | together for the benefit of LOAD. if we regard a Common Lisp source file as a sequence of individual top-level forms that does not know about file boundaries between them, you can easily concatenate source files and end up with something that can be loaded as a unit. if we regard the compiled fasl files the same way, and this can obviously be done if each top-level form is saved to disk individually, possibly including some file-specific prologue that is generated by the compiler, there really is nothing special involved in concatenating files. if you can load from a stream, you can load from a concatenated-stream, so there should already be support in the standard for the whole concept. #:Erik