[Openmcl-devel] Maybe a better way to delivery apps
ron at flownet.com
Sun Jun 9 08:09:51 PDT 2013
4.10. Concatenating FASL Files
Multiple fasl files can be concatenated into a single file.
fasl-concatenate out-file fasl-files &key (:if-exists :error)
Concatenate several fasl files, producing a single output file.
Arguments and Values:
out-file--- Name of the file in which to store the concatenation.
fasl-files--- List of names of fasl files to concatenate.
:if-exists--- As for OPEN, defaults to :error
Creates a fasl file which, when loaded, will have the same effect as loading the individual input fasl files in the specified order. The single file might be easier to distribute or install, and loading it may be at least a little faster than loading the individual files (since it avoids the overhead of opening and closing each file in succession.)
The PATHNAME-TYPE of the output file and of each input file defaults to the current platform's fasl file type (.dx64fsl or whatever.) If any of the input files has a different type/extension an error will be signaled, but it doesn't otherwise try too hard to verify that the input files are real fasl files for the current platform.
On Jun 9, 2013, at 6:57 AM, Mike Manilone wrote:
> Hi all,
> I think that delivering apps may be easier if CCL provides something
> similar to JAR (LAR)... A compressed file is much smaller than a core
> image or a huge executable. Maybe a bundle of FASLs? The compilation may
> depend on ASDF.
> Any comments?
> | Mike Manilone (ekd123) |
> | http://www.ekd123.org |
> Openmcl-devel mailing list
> Openmcl-devel at clozure.com
More information about the Openmcl-devel