On Mon, Jun 14, 2010 at 2:10 PM, Mark Evenson <evenson.not.org@gmail.com> wrote:
[Ticket #100 filed to track this issue][1].
Thanks for officially tracking the problem. I think that "fixing" it only for asdf is simple: just emit (parse-namestring "...") instead of #P"...". That would allow to re-release 0.20 quickly. I can send a patch tonight for that. Eliminating the problem in the general case is harder and we'd better discuss the possible solutions. Here's my take at it: 1) don't fix it. State clearly that literal pathnames in source are OS-dependent. 2) keep, for each pathname constructed via #P or parse-namestring, the string passed by the user, until the pathname is destructively modified. When dumping it, use that string if available, else warn and use a calculated string. 3) dump-object for pathnames outputs a MAKE-PATHNAME form that reconstructs the pathname component by component. what do you think? Bye, Alessio