Dear Xiaofeng,
assuming it's indeed a bug in allegro 8.1's compile-file-pathname, can you try to edit the call to compile-file-pathname this way, in defun compile-file-pathname* ?
(apply 'compile-file-pathname input-file (remove-keys `(#+(and allegro (not (version>= 8 2))) :external-format ,@(unless output-file '(:output-file))) keys))
—♯ƒ • François-René ÐVB Rideau •Reflection&Cybernethics• http://fare.tunes.org Philosophy is questions that may never be answered. Religion is answers that may never be questioned.
On Sat, Jan 12, 2013 at 12:48 AM, Raymond Toy toy.raymond@gmail.com wrote:
"Fare" == Far <Far> writes:
Fare> Dear Xf, Fare> thanks for the patch. On allegro 8.1, is it only compile-file-pathname Fare> that refuses the :external-format argument, or compile-file as well? Fare> In the latter case, how does allegro 8.1 control encoding for input Fare> files? Does it rely on a special variable?Is this not a bug in Allegro's compile-file-pathname. The CLHS says compile-file-pathname should accept all keywords accepted by compile-file.
The docs for Allegro 8.1[1] says compile-file accepts :external-format.
Ray [1] http://www.franz.com/support/documentation/8.1/ansicl/dictentr/compile-.htm
asdf-devel mailing list asdf-devel@common-lisp.net http://lists.common-lisp.net/cgi-bin/mailman/listinfo/asdf-devel