CL:OPEN failure

[Mark Evenson]

The following form

(open #p"~/xx" :direction :output
               :if-exists :append
               :external-format '(:latin-1 :eol-style :lf))

fails with the following message

; Evaluation aborted on NIL.

[Mark Evenson]

Running outside of SLIME gives the more intelligible

java.nio.charset.UnsupportedCharsetException: LATIN-1
	at java.nio.charset.Charset.forName(Charset.java:531)
	at org.armedbear.lisp.util.RandomAccessCharacterFile.setEncoding(RandomAccessCharacterFile.java:309)
	at org.armedbear.lisp.util.RandomAccessCharacterFile.<init>(RandomAccessCharacterFile.java:288)

Why does SLIME not return a meaningful error?

Should we add some sort of alias for LATIN-1

[Mark Evenson]

Observation: UnsupportedCharsetException? is a Java runtime exception.

Hypothesis: The SLIME :spawn communication style is not correctly communicating the runtime exception back to the SWANK listener.

[Mark Evenson]

Triggering the runtime exception via

(jstatic "forName" "java.nio.charset.Charset" "foo")

shows that SLIME does seem to work with RuntimeException?.

Maybe the difference is that the RuntimeException? is occurring inside nested constructors?

Recommendation: signal a meaningful Lisp condition when an invalid charset is used.

[Mark Evenson]

SIMPLE-ERROR now signaled for invalid encodings in r14735.

Unsure if there is still a problem lurking in how SLIME interacts with Java exceptions thrown by the ABCL implementation, but closing for now.