> Please provide some documentation of pathname objects "(with no namestring)"
> the behaviour is sometimes less than obvious.
Possibly, though the existence of pathnames with no namestrings is a
direct conclusion from the specification, so it's not clear what extra
information can be provided by documenting them. (In general, I don't
think the sbcl manual is the place for resolving every simple confusion
any user has ever had: there are perfectly good introductory CL texts,
some of which even discuss pathnames in some detail).
> Really, why signal a SIMPLE-ERROR around the NAMESTRING callpoint
> instead of signaling a FILE-ERROR when MAKE-PATHNAME recieved a :type
> specifier a its sole argument?
This is easy to answer: because the pathnames that have no namestrings
can be merged with other pathnames.
status wishlist
done
mon_key <email address hidden> writes:
> Please provide some documentation of pathname objects "(with no namestring)"
> the behaviour is sometimes less than obvious.
Possibly, though the existence of pathnames with no namestrings is a
direct conclusion from the specification, so it's not clear what extra
information can be provided by documenting them. (In general, I don't
think the sbcl manual is the place for resolving every simple confusion
any user has ever had: there are perfectly good introductory CL texts,
some of which even discuss pathnames in some detail).
> Really, why signal a SIMPLE-ERROR around the NAMESTRING callpoint
> instead of signaling a FILE-ERROR when MAKE-PATHNAME recieved a :type
> specifier a its sole argument?
This is easy to answer: because the pathnames that have no namestrings
can be merged with other pathnames.
Christophe