On 5/25/10 May 25 -11:11 AM, Faré wrote:
I'm not sure what you want, but try for current directory, .. for up,
etc.
.. is actually not recognized by ASDF but passed to the
implementation, and from it to the OS.
I added a test that verifies that works as a pathname component. I
wasn't sure
On 5/25/10 May 25 -11:11 AM, Faré wrote:
I'm not sure what you want, but try for current directory, .. for up,
etc.
.. is actually not recognized by ASDF but passed to the
implementation, and from it to the OS.
Question: if .. is handled by the OS, does that mean it may not be
portable
On 26 May 2010 09:20, Robert Goldman rpgold...@sift.info wrote:
On 5/25/10 May 25 -11:11 AM, Faré wrote:
I'm not sure what you want, but try for current directory, .. for up,
etc.
.. is actually not recognized by ASDF but passed to the
implementation, and from it to the OS.
Question: if
On 5/26/10 May 26 -9:35 AM, Faré wrote:
On 26 May 2010 09:18, Robert Goldman rpgold...@sift.info wrote:
On 5/25/10 May 25 -11:11 AM, Faré wrote:
I'm not sure what you want, but try for current directory, .. for up,
etc.
.. is actually not recognized by ASDF but passed to the
What's the right syntax for specifying a relative pathname for a module
whose files should live in the parent directory instead of in a
subdirectory?
E.g., if I have
(:module foo
:components ((:file bar) (:file baz))
:pathname
)
what goes in there if I do NOT want the files to live in
