I’ve got to push back on your rant. There’s a perfectly good reason for those two limitations you dislike: they are the same as the limitations on logical pathnames. So if you wish to be able to find an ASDF system relative to a directory designated by a logical pathname, those limitations are pretty much forced on you. Additionally, mixed case is a pain for people who want to refer to systems with symbols instead of strings, a common practice On Sep 14, 2024 at 00:00:05 CDT, Robert Dodier robert.dodier@gmail.com wrote: I am interested in automatically generating ASDF system definitions for projects which lack them. These projects have names, both the project name and the names of files or directories within them, which might not conform to ASDF's requirements for names.
In particular, project names containing uppercase letters and underscores.These are other peoples' projects, so I'm not at liberty to rename them to conform to ASDF.
RANT. The limitations that ASDF puts on names are just bananas. I have to wonder who thought it would be a good idea to force people to work around them. I know this has been discussed before, without any resolution, so I won't pursue it any further. There's no need to explain about logical pathnames, I know already. Thanks for understanding. /RANT
For a project which has a conforming name, say foobar, I can create foobar.asd and say that the name of the system is "foobar". That's great. Let's say the name of the project is Foo_Bar. What are some options for naming the .asd system and the system which it contains, ideally so that when a user tries (asdf:load-system "Foo_Bar") they get the appropriate system?
Perhaps that's impossible; if so I'd just like to know.
I've tried some different things and haven't come up with anything that seems to work. A web search finds a few aging and/or obsolete references, and in any event, nothing specifically directed towards solving this problem.
Thanks for any insights.
Robert Dodier