quicklisp not finding systems in local-projects
On 2016/11/24 07:02, Mike Maul wrote:
Tried in version 1.4 and also built from source.
Both versions work for me (except in Java 9). Can you provide the values of LISP-IMPLEMENTATION-VERSION? And perhaps a little bit of how to reproduce your problems? -- "A screaming comes across the sky. It has happened before, but there is nothing to compare to it now."
The problem happens when there are files/directories with an asterisk (*) in the name. I was able to resolve this by not raising an error in FILE_DIRECTORY_P in probe_file.java if the name returns a asterisk (*). My question is should I file a bug report and send a patch or should I raise and issue with Quicklisp and send a pull request handling the FileError in Quicklisp? My thoughts are well if a file can contain a asterisk the an error shouldn't be raised... On Thu, Nov 24, 2016 at 1:02 AM, Mike Maul <mike.maul@gmail.com> wrote:
Tried in version 1.4 and also built from source.
On 2016/11/25 05:46, Mike Maul wrote:
The problem happens when there are files/directories with an asterisk (*) in the name. I was able to resolve this by not raising an error in FILE_DIRECTORY_P in probe_file.java if the name returns a asterisk (*). My question is should I file a bug report and send a patch or should I raise and issue with Quicklisp and send a pull request handling the FileError in Quicklisp?
My thoughts are well if a file can contain a asterisk the an error shouldn't be raised...
Please send the patch to this mailing list (or me directly). I will look at this issue. At this time, I don't think this is an issue with Quicklisp, but rather ABCL, but I will help get the right parties to fix things if this turns out not to be the case. Since asterisk is a legal character on many (all?) filesystems, it needs to have a representation somehow in a PATHNAME. What has never been clear to me was how the ANSI standard allows one to specify a literal asterisk chararcter versus a wildcard. I need to study up a bit on other implementations, as well as the standard. In any case, ABCL should not cause such errors when PROBE-{DIRECTORY,FILE} works on filesystems containing asterisk characters. In any event, [we already logged a ticket for this issue from John Pallister][391]. [391]: http://abcl.org/trac/ticket/391 -- "A screaming comes across the sky. It has happened before, but there is nothing to compare to it now."
participants (2)
-
Mark Evenson -
Mike Maul