- PVE's regression tests want them to raise errors. SBCL
- generates the infinities instead, which may or may not be
- conforming behavior, but then blow it by being unable to
- output the infinities, since support for infinities is generally
- broken, and in particular SB-IMPL::OUTPUT-FLOAT-INFINITY is
- undefined.
- * (in section12.erg) various forms a la
- (FLOAT 1 DOUBLE-FLOAT-EPSILON) don't give the right behavior.
-
-* type safety errors reported by Peter Van Eynde July 25, 2000:
- * (COERCE (QUOTE (A B C)) (QUOTE (VECTOR * 4)))
- => #(A B C)
- In general lengths of array type specifications aren't
- checked by COERCE, so it fails when the spec is
- (VECTOR 4), (STRING 2), (SIMPLE-BIT-VECTOR 3), or whatever.
- * CONCATENATE has the same problem of not checking the length
- of specified output array types. MAKE-SEQUENCE and MAP and
- MERGE also have the same problem.
- * (COERCE 'AND 'FUNCTION) returns something related to
- (MACRO-FUNCTION 'AND), but ANSI says it should raise an error.
- * ELT signals SIMPLE-ERROR if its index argument
- isn't a valid index for its sequence argument, but should
- signal TYPE-ERROR instead.
- * FILE-LENGTH is supposed to signal a type error when its
- argument is not a stream associated with a file, but doesn't.
- * (FLOAT-RADIX 2/3) should signal an error instead of
- returning 2.
- * (LOAD "*.lsp") should signal FILE-ERROR.
- * (MAKE-CONCATENATED-STREAM (MAKE-STRING-OUTPUT-STREAM))
- should signal TYPE-ERROR.
- * MAKE-TWO-WAY-STREAM doesn't check that its arguments can
- be used for input and output as needed. It should fail with
- TYPE-ERROR when handed e.g. the results of MAKE-STRING-INPUT-STREAM
- or MAKE-STRING-OUTPUT-STREAM in the inappropriate positions,
- but doesn't.
- * (PARSE-NAMESTRING (COERCE (LIST #\f #\o #\o (CODE-CHAR 0) #\4 #\8)
+ PVE's regression tests want them to raise errors. SBCL
+ generates the infinities instead, which may or may not be
+ conforming behavior, but then blow it by being unable to
+ output the infinities, since support for infinities is generally
+ broken, and in particular SB-IMPL::OUTPUT-FLOAT-INFINITY is
+ undefined.
+ d: (in section12.erg) various forms a la
+ (FLOAT 1 DOUBLE-FLOAT-EPSILON)
+ don't give the right behavior.
+
+46:
+ type safety errors reported by Peter Van Eynde July 25, 2000:
+ a: (COERCE (QUOTE (A B C)) (QUOTE (VECTOR * 4)))
+ => #(A B C)
+ In general lengths of array type specifications aren't
+ checked by COERCE, so it fails when the spec is
+ (VECTOR 4), (STRING 2), (SIMPLE-BIT-VECTOR 3), or whatever.
+ b: CONCATENATE has the same problem of not checking the length
+ of specified output array types. MAKE-SEQUENCE and MAP and
+ MERGE also have the same problem.
+ c: (COERCE 'AND 'FUNCTION) returns something related to
+ (MACRO-FUNCTION 'AND), but ANSI says it should raise an error.
+ d: ELT signals SIMPLE-ERROR if its index argument
+ isn't a valid index for its sequence argument, but should
+ signal TYPE-ERROR instead.
+ e: FILE-LENGTH is supposed to signal a type error when its
+ argument is not a stream associated with a file, but doesn't.
+ f: (FLOAT-RADIX 2/3) should signal an error instead of
+ returning 2.
+ g: (LOAD "*.lsp") should signal FILE-ERROR.
+ h: (MAKE-CONCATENATED-STREAM (MAKE-STRING-OUTPUT-STREAM))
+ should signal TYPE-ERROR.
+ i: MAKE-TWO-WAY-STREAM doesn't check that its arguments can
+ be used for input and output as needed. It should fail with
+ TYPE-ERROR when handed e.g. the results of
+ MAKE-STRING-INPUT-STREAM or MAKE-STRING-OUTPUT-STREAM in
+ the inappropriate positions, but doesn't.
+ j: (PARSE-NAMESTRING (COERCE (LIST #\f #\o #\o (CODE-CHAR 0) #\4 #\8)