453 |
93. READTABLE-CASE is undefined (and its SETF form) |
93. READTABLE-CASE is undefined (and its SETF form) |
454 |
ansi-tests: read-symbol.1[678] read-symbol.25 |
ansi-tests: read-symbol.1[678] read-symbol.25 |
455 |
readtable-case.* set-syntax-from-char-trait-* |
readtable-case.* set-syntax-from-char-trait-* |
456 |
|
print.symbol.[123456789] print-symbol.1[012] prin1.symbol.[123] |
457 |
|
|
458 |
|
|
459 |
94. Binding *READ-SUPPRESS* to true doesn't totally suppress reading; |
94. Binding *READ-SUPPRESS* to true doesn't totally suppress reading; |
460 |
reading a list still returns a list, as does reading a vector |
reading a list still returns a list, as does reading a vector |
970 |
212. COMPUTE-APPLICABLE-METHODS should signal a program-error when called |
212. COMPUTE-APPLICABLE-METHODS should signal a program-error when called |
971 |
with too many or too few arguments in safe code. |
with too many or too few arguments in safe code. |
972 |
ansi-tests: compute-applicable-methods.error.1 |
ansi-tests: compute-applicable-methods.error.1 |
973 |
|
|
974 |
|
213. FIND-METHOD should signal a program-error when called with too few |
975 |
|
or too many arguments. |
976 |
|
ansi-tests: find-method.error.[1234] |
977 |
|
|
978 |
|
214. FIND-METHOD should signal an error if the length of the specializers |
979 |
|
list does not equal the number of required arguments to the generic |
980 |
|
function |
981 |
|
ansi-tests: find-method.error.[789] find-method.error.10 |
982 |
|
|
983 |
|
215. ADD-METHOD should signal a program-error when called with too few or |
984 |
|
too many arguments in safe code. |
985 |
|
ansi-tests: add-method.error.[456] |
986 |
|
|
987 |
|
216. ADD-METHOD should return the generic function. |
988 |
|
ansi-tests: add-method.[12] |
989 |
|
|
990 |
|
217. Computing SLOT-VALUE on a missing slot should throw an UNBOUND-SLOT error. |
991 |
|
ansi-tests: unbound-slot.[12] |
992 |
|
|
993 |
|
218. A generic function should throw a program-error if called with too few |
994 |
|
or too many arguments in safe code. |
995 |
|
ansi-tests: defmethod.error.1[34] |
996 |
|
|
997 |
|
219. A generic function should throw a program-error when called with invalid |
998 |
|
keyword arguments in safe code. |
999 |
|
ansi-tests :defmethod.error.15 |
1000 |
|
|
1001 |
|
220. Double floats are not printed readably correctly. Round-off error |
1002 |
|
is apparently occuring, causing the re-read value to differ slightly. |
1003 |
|
ansi-tests: print.double-float.random print.long-float.random |
1004 |
|
|
1005 |
|
221. #\Space should print (under PRIN1) as #\ , not #\Space. |
1006 |
|
ansi-tests: print.char.4 print.char.10 |
1007 |
|
|
1008 |
|
222. Escaped haracter printing violates therules in 2.4.8.1 |
1009 |
|
ansi-tests: print.char.7 |
1010 |
|
|
1011 |
|
223. (code-char 28) doesn't print or possibly read correctly |
1012 |
|
ansi-tests: print.char.[89] |
1013 |
|
|
1014 |
|
224. A symbol whose symbol-package is a deleted package should be printed |
1015 |
|
as if it had no home package. |
1016 |
|
ansi-tests: print.symbol.prefix.8 |
1017 |
|
|
1018 |
|
225. Component printing controlled by *print-level* should not print # |
1019 |
|
for an object unless that object 'has components'. I interpret |
1020 |
|
this to mean objects that are printed by recursive calls to the |
1021 |
|
object printer, and that can be targets of #n# syntax, so cons cells, |
1022 |
|
T vectors, structures, etc. have components, but not numbers, symbols. |
1023 |
|
strings, or bit vectors. |
1024 |
|
ansi-tests: print.cons.level.[25] print.vector.level.[34] |
1025 |
|
|
1026 |
|
226. Arrays of dimension > 1 that have total size > 0 and one ore more |
1027 |
|
dimensions of size 0 do not print readably. |
1028 |
|
ansi-tests: print.array.2.2[123] |
1029 |
|
|
1030 |
|
227. The 'is-similar*' generic function is not dispatching properly. |
1031 |
|
In particular, the correct method is apparently not being invoked |
1032 |
|
on pathnames. |
1033 |
|
ansi-tests: print.pathname.1 |
1034 |
|
|
1035 |
|
228. PPRINT-FILL should signal a program-error when called with the |
1036 |
|
wrong number of arguments in safe code. |
1037 |
|
ansi-tests: pprint-fill.error.[123] |
1038 |
|
|
1039 |
|
229. PPRINT-LINEAR should signal a program-error when called with the |
1040 |
|
wrong number of arguments in safe code. |
1041 |
|
ansi-tests: ppprint-linear.error.[123] |