[armedbear-devel] Patch for ASDF2 to use arbitrary output translation function
alanruttenberg at gmail.com
Thu Mar 25 16:17:04 UTC 2010
Sorry, haven't had a chance to look closely at asdf2, but wanted to
point out that in certain contexts, like running applets, writing to
any file system is prohibited. For those cases, it would be nice if it
was super-easy to set a flag that says: if there isn't a compiled
version, or if it is stale, don't try to compile - just load source.
On Thu, Mar 25, 2010 at 8:38 AM, Mark Evenson <evenson at panix.com> wrote:
> On 3/25/10 2:39 PM, Mark Evenson wrote:
>> I'm working on an implementation of this on your git version as a
>> proof of concept, but haven't gotten much further than getting your
>> output configuration to accept the new syntax. I assume that
>> actually applying the function will be easy, but I am not sure.
> Attached please find a patch to implement the use of an arbitrary output
> translation function in ASDF2.
> An example of the use would be the directive
> (#p"jar:file:/**/*.jar!/**/*.*" :function translate-jar-pathname)
> which will call the function TRANSLATE-JAR-PATHNAME on a match of the first
> element of the list. The function will be invoked with two arguments, the
> first being the matching wildcard, and the second being the pathname to be
> translated. The function returns the translation.
> Hopefully, after review and critique, we can can get something like this in
> With the attached patch to abcl trunk, I can successfully use ASDF2 to load
> ASDF systems in jar files, with the compiled files being output to a
> translation under :USER-CACHE.
> "A screaming comes across the sky. It has happened before, but there
> is nothing to compare to it now."
> armedbear-devel mailing list
> armedbear-devel at common-lisp.net
More information about the armedbear-devel