Author: yamakenz
Date: Sun Feb 24 07:58:13 2008
New Revision: 5240

Modified:
  sigscheme-trunk/src/port.c
  sigscheme-trunk/test/test-string.scm

Log:
* src/port.c
 - (scm_special_char_table): Remove the escape sequence "\|"
   invalidated in final R6RS. Thanks for the anonymous reporter
* test/test-string.scm
 - Follow the change. And make check has been passed


Modified: sigscheme-trunk/src/port.c
==============================================================================
--- sigscheme-trunk/src/port.c  (original)
+++ sigscheme-trunk/src/port.c  Sun Feb 24 07:58:13 2008
@@ -78,9 +78,6 @@
    {'\"',   "\\\"",  "\""},         /* 34, R5RS */
    {'\\',   "\\\\",  "\\"},         /* 92, R5RS */
    {' ',    " ",     "space"},      /* 32, R5RS */
-#if SCM_USE_R6RS_CHARS
-    {'|',    "\\|",   "|"},
-#endif

    /* control characters */
    {'\n',   "\\n",   "newline"},    /*  10, R5RS */

Modified: sigscheme-trunk/test/test-string.scm
==============================================================================
--- sigscheme-trunk/test/test-string.scm        (original)
+++ sigscheme-trunk/test/test-string.scm        Sun Feb 24 07:58:13 2008
@@ -98,7 +98,8 @@
(assert-equal? (tn) (integer->string 11)          "\v")  ;; 118
(assert-equal? (tn) (list->string '(#\vtab))      "\v")  ;; 118
(assert-equal? (tn) '(#\vtab)   (string->list    "\v"))  ;; 118
-(assert-equal? (tn) (integer->string 124)         "\|")  ;; 124
+;; "\|" is removed from final R6RS
+;;(assert-error  (tn) (integer->string 124)         "\|")  ;; 124

;; All these conventional escape sequences should cause parse error as defined
;; in SRFI-75: "Any other character in a string after a backslash is an
@@ -197,7 +198,8 @@
(assert-parse-error (tn) "\"\\y\"")  ;; 121
(assert-parse-error (tn) "\"\\z\"")  ;; 122
(assert-parse-error (tn) "\"\\{\"")  ;; 123
-;;                            "\|"   ;; 124
+;; "\|" is removed from final R6RS
+(assert-parse-error (tn) "\"\\|\"")  ;; 124
(assert-parse-error (tn) "\"\\}\"")  ;; 125
(assert-parse-error (tn) "\"\\~\"")  ;; 126

Reply via email to