Comment 2 for bug 1642737

Right; aside from the :version field, *wild-file-for-directory* and *wild-file* only differ on clisp and gcl. So my comparison of the two was unfair.

I think the point I wanted to make is: It's great to have a function like directory-files or subdirectories, assuming they work correctly. And to implement them, it might make sense to define certain wildcard objects like *wild-file*. I'm just not sure if I understand why they're public.

If I want to find all files by the name *.log in a directory, will uiop:*wild-file* help me create a wild pathname in a portable fashion or why would I need those objects? Are they not implementation details?

PS: interestingly, the TODO file contains this line:
*** fix directory-files to not return directories on CCL, etc. Add tests.
Not only do I not observe such a problem, my comments from earlier also suggested that CCL is the only implementation that tended to *exclude* directories when every other implementation included them. So this seems a bit backwards.