[My apologies if you receive multiple copies of this email.]
Hi everybody!
As some of you will know, I'll start on a new job tomorrow. This new
job won't involve much hacking, if at all, and thus it doesn't look
like I'll have a lot of time to maintain my open source libraries in
the near future. I have no plans to suddenly disappear from the CL
world, but don't expect new releases of any of my libs any time soon.
(At least none published by me or on my server.)
Luckily, Hans Hübner - who already did most of the maintenance and
development work for Hunchentoot in the last two years or so - offered
to coordinate further development via github. See his full
announcement at
<http://netzhansa.blogspot.com/2011/08/ediware-moving-to-github.html>.
I'll continue to read the mailing lists for my libs and I'm still
interested in fixing bugs you might find in the release tarballs
available on my web server. However, I will likely not bother to
discuss or work on new features or compatibility code for
implementations other than LispWorks (which happens to be the one I'm
using).
Lastly, I hope to see a lot of you in Amsterdam
<http://weitz.de/eclm2011/> in October. The number of registrations
so far has been pretty disappointing, but you still have three weeks
left to change your mind... :)
Take care,
Edi.
I reported a related problem some time ago
http://lists.common-lisp.net/pipermail/cl-ppcre-devel/2011-January/000706.h…
However, instead of the values I supplied now cl-unicode is using
:unspecific for the :type of a pathname.
(defun dump-derived-tests ()
"Parses the Unicode data file \"DerivedCoreProperties.txt\" \(which
is not used in read.lisp) and uses it to create a file
\"derived-properties\" which will be used by CL-UNICODE-TEST."
(with-output-to-source-file (out (make-pathname :name "derived-properties"
:type :unspecific
:directory '(:relative :up
"test"))
:no-header-p t)
This is not supported by ECL, which uses NIL to represent an unfilled value
(absent therefore). From the Hyperspec
http://www.lispworks.com/documentation/HyperSpec/Body/19_bbbc.htm
A conforming program must never unconditionally use a :unspecific as the
value of a pathname component because such a value is not guaranteed to be
permissible in all implementations.
Probably what you want to solve is the merge-pathnames above the code (in
the macro), which might instead read
`(let* ((directory (make-pathname :name nil :type nil :version nil
:defaults *this-file*))
(pathname (merge-pathnames ,relative-path directory))
Cheers,
Juanjo
--
Instituto de Física Fundamental, CSIC
c/ Serrano, 113b, Madrid 28006 (Spain)
http://juanjose.garciaripoll.googlepages.com
