On Sun, Dec 18, 2011 at 1:36 PM, Anton Kovalenko <an...@sw4me.com> wrote: >> In this case, the error's LIBRARY-SPECIFICATION slot (or something >> along those lines), could hold a string, a pathname, or s-exps whose >> CARs are one of :OR, :DEFAULT, or :FRAMEWORK. > > When we want to provide a restart for automatic library installation, > the most useful thing is a list of *all pathnames actually tried*. > > We know that before the error is signalled, every pathname possible (for > current implementation's feature set) has been tried. Collecting them > along the way shouldn't be hard. And I can't think of an > "auto-installer" (or anything external to CFFI) for which the details of > *why* those pathnames were used are somehow relevant.
Excellent point. I like this solution. -- Luís Oliveira http://r42.eu/~luis/ _______________________________________________ cffi-devel mailing list cffi-devel@common-lisp.net http://lists.common-lisp.net/cgi-bin/mailman/listinfo/cffi-devel
