Please try 2.016.1 and see if it satisfies you.
Pathnames are a big FAIL of CL.
—♯ƒ • François-René ÐVB Rideau •Reflection&Cybernethics• http://fare.tunes.org
Slogans rarely convince the unconvinced. However, they do rally the troops
already on your side. — John McCarthy
> On re-reading CLHS, I retract my admission that ABCL is non-conformant.
> From the CLHS glossary a "valid pathname device [is a] a string, nil,
> :unspecific, or some other object defined by the implementation to be a
> valid pathname device." ABCL is using the "some other object" ability here.
A user question:
011 13:28, Erik Winkels wrote:
> Hi,
>
> I'm not sure whether ASDF is the culprit here but I need some help tracking
> down a problem I'm having:
>
> I'm developing a program which gets called from the command line so I'm also
> testing it like that. i.e. I'm using the classic
On 6/9/11 7:42 PM, Mark Evenson wrote:
[…]
As I mentioned in the previous message, I think the better fix is to
have TRANSLATE-JAR-PATHNAME do something like the following (untested):
The patch is bogus as a direct fix. Something (TRUENAMIZE?) has
stripped the :unspecific device component by
On 6/9/11 7:06 PM, Faré wrote:
Thanks for thinking with me on this.
OK. I believe the following definition might make
each of Stelian, you and I happy. Can you try it?
(defun* compile-file-pathname*
(input-file&rest keys&key output-file&allow-other-keys)
(if (absolute-pathname-p output
On 6/9/11 6:44 PM, Faré wrote:
Note that when I (describe #p"jar:file:///foo/bar.jar!/baz/quux.lisp")
I get:
#P"jar:file:/foo/bar.jar!/baz/quux.lisp" is an object of type
EXTENSIONS:JAR-PATHNAME:
HOST NIL
DEVICE (#P"/foo/bar.jar")
DIRECTORY(:ABSOLUTE "baz")
N
>> Thanks for thinking with me on this.
OK. I believe the following definition might make
each of Stelian, you and I happy. Can you try it?
(defun* compile-file-pathname*
(input-file &rest keys &key output-file &allow-other-keys)
(if (absolute-pathname-p output-file)
(apply 'compile-f
>> Note that when I (describe #p"jar:file:///foo/bar.jar!/baz/quux.lisp")
>> I get:
>> #P"jar:file:/foo/bar.jar!/baz/quux.lisp" is an object of type
>> EXTENSIONS:JAR-PATHNAME:
>> HOST NIL
>> DEVICE (#P"/foo/bar.jar")
>> DIRECTORY (:ABSOLUTE "baz")
>> NAME "q
On 6/9/11 16:37 , Faré wrote:
[…]
Can you write a simple test to be added to test/asdf-pathnames.script,
I'll work on that. Can I just create a new top-level form or do you
prefer I wedge it into TEST-COMPONENT-PATHNAMES with an #+abcl/#-abcl
conditional?
and/or send me an example such t
On 9 June 2011 09:35, Mark Evenson wrote:
> Stellian's [normalization to ANSI semantics of COMPILE-FILE-PATHNAME*][1]
> has the unfortunate effect of breaking ABCL's translation of systems
> packaged in jar files.
>
Oops. This wasn't caught by my tests. My sincere apologies.
Can you write a simple
Stellian's [normalization to ANSI semantics of
COMPILE-FILE-PATHNAME*][1] has the unfortunate effect of breaking ABCL's
translation of systems packaged in jar files.
[1]:
http://common-lisp.net/gitweb?p=projects/asdf/asdf.git;a=commit;h=ed4cd32932e937724b0b28d1c20ed6abe5d58dc0;js=1
I have ap
11 matches
Mail list logo