[I CC just in case the ECL mailing list provides me a better answer]
In polishing the upcoming ECL release I discovered that there are two
problems when trying to compile cl-unicode. One is due to a bug in ECL, the
other one is due to what I believe an error in CL-UNICODE. More precisely,
in build/dump.lisp I find
(with-output-to-source-file (out (make-pathname :name "derived-properties"
:type :unspecific
:directory '(:relative :up
"test"))
:no-header-p t)
As far as I know, :UNSPECIFIC is reserved for values that do not make sense
for a filesystem, but in this particular case what happens is that the file
does not have a file extension, not that extensions (types) do not exist at
all.
The consequence is that this lisp form creates an unprintable pathname (one
which cannot be written "readably"), both in ECL and CLISP, and ECL
righteously complains that this file can not be opened.
I believe the appropriate line should be ":type nil", which works on SBCL,
CLISP and ECL, AFAIK.
Am I wrong?
Juanjo
P.S.: This is cl-unicode 0.1.1 distributed by quicklisp.
--
Instituto de Física Fundamental, CSIC
c/ Serrano, 113b, Madrid 28006 (Spain)
http://juanjose.garciaripoll.googlepages.com
------------------------------------------------------------------------------
Protect Your Site and Customers from Malware Attacks
Learn about various malware tactics and how to avoid them. Understand
malware threats, the impact they can have on your business, and how you
can protect your company and customers by using code signing.
http://p.sf.net/sfu/oracle-sfdevnl
_______________________________________________
Ecls-list mailing list
Ecls-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ecls-list
