> Greetings! GCL carries around its own modules in libgcl.a for
> compiler::link and the like. Using an absolute pathname for
> modules makes no sense, as they will be extracted from the archive
> the current directory. I propose reserving the designator "gcl_"
> the start of the pathname-name to indicate that truename init-names
> are not to be used. The rest of the namespace would belong to
> user and write the full pathname of the source in the initname.
> I.e. this will fail if the user has two files identically named
> gcl_.... at two distinct locations in their source tree. Does
> sound acceptable?
The general idea sounds OK to me -- I don't see any
files so named in our code base, nor in the ACL2 2.9.2 distribution.