kondratjevsk at gmail.com
Sun Feb 2 22:58:42 UTC 2014
Thanks, that's clear.
As for the fix, that's perhaps too much of a feat for me. :) But I'll think
2014-02-02 Faré <fahree at gmail.com>:
> It's a bug indeed. Unhappily, DIRECTORY is not portable at all. I've
> added an ugly workaround in 22.214.171.124.
> If you're volunteering to commit a real fix, and tests, to make sure
> it works on each and every of the 10+ supported implementations,
> together with a regression test, I'll be delighted to commit it.
> —♯ƒ • François-René ÐVB Rideau •Reflection&Cybernethics•
> The urge to save humanity is almost always a false front for the urge to
> — H. L. Mencken
> On Sat, Feb 1, 2014 at 3:13 PM, Станислав Кондратьев
> <kondratjevsk at gmail.com> wrote:
> > Hello,
> > I tried uiop and discovered two issues.
> > I had installed uiop using quicklisp.
> > The first issue looks like a bug: if I list the files of my home
> > in CLISP, every file is included in the list twice as if the directory
> > listed two times. This takes place no matter if I specify the directory
> > "~/" or spell it out, and also if I run CLISP in my home directory and
> > uiop/os:getcwd. However, the function works normally with directories
> > than the home one. I did not specify wildcards in either case. I have
> > observed this behaviour on Debian and OpenSuse.
> > The second issue looks like a discrepancy between implementations: while
> > CLISP uiop/filesystem:directory-files returns a list of files (not
> > subdirectories), in SBCL the directories are included into the output. I
> > wonder at least which behaviour is the intended one.
> > Best regards,
> > Stanislav.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the asdf-devel