guile/guile-core BUGS

[Thien-Thi Nguyen]

CVSROOT:        /cvs
Module name:    guile
Changes by:     Thien-Thi Nguyen <address@hidden>       01/11/19 18:08:02

Modified files:
        guile-core     : BUGS 

Log message:
        (11): Set "fixed: no-need".

CVSWeb URLs:
http://savannah.gnu.org/cgi-bin/viewcvs/guile/guile-core/BUGS.diff?cvsroot=OldCVS&tr1=1.11&tr2=1.12&r1=text&r2=text

Patches:
Index: guile/guile-core/BUGS
diff -u guile/guile-core/BUGS:1.11 guile/guile-core/BUGS:1.12
--- guile/guile-core/BUGS:1.11  Sat Nov 17 06:43:28 2001
+++ guile/guile-core/BUGS       Mon Nov 19 18:08:02 2001
@@ -14,6 +14,9 @@
 line 0 is empty (newline always follows newpage (recognizable w/ "\f\n")).
 The suggested regexps can be used in a line-oriented parser.
 
+You can use "fixed: no-need (EXPLANATION)" if the bug doesn't need to be
+fixed.  EXPLANATION might be "not a bug", "user error", etc.
+
 
 bug 0 -- no BUGS file
 reported-by: ttn / 2001-09-25
@@ -235,7 +238,7 @@
 
 bug 11 -- (ice-9 optargs) #:rest arg polluted by keys/values
 reported-by: ttn / 2001-11-09
-fixed: not-yet
+fixed: no-need (behavior consistent w/ Common Lisp, user error)
 
 ttn sez:
 > the following code displays
@@ -264,6 +267,17 @@
 >   (blah #:j 'JAY #:k 'KAY)
 >   (blah #:j 'JAY #:k 'KAY 1)
 >   (blah #:j 'JAY #:k 'KAY '(1 2 3))
+
+mvo sez:
+> In Common Lisp, there are no non-key rest-args when you have keyword
+> parameters.  After the required and optional arguments, there must
+> follow an even number of additional arguments, and every two of them
+> are treated as a keyword/value pair.
+>
+> I think it makes sense the way CL specifies this.  Anything beyond
+> this would lead to confusion.  If you want to go beyond what (ice-9
+> optargs) offers, yo are probably best off writing your own argument
+> parser.
 
 
 [BUGS ends here]