[ Usenet FAQs | Search | Web FAQs | Documents | RFC Index ]
Part1 - Part2 - Part3 - Part4 - Part5 - Part6 - Part7 - Single Page
Top Document: FAQ: Lisp Frequently Asked Questions 3/7 [Monthly posting]
Previous Document: [3-0] Why does (READ-FROM-STRING "foobar" :START 3) return FOOBAR instead of BAR?
Next Document: [3-2] Why can't I apply #'AND and #'OR?
-
Search the FAQ Archives
Part1 - Part2 - Part3 - Part4 - Part5 - Part6 - Part7 - Single Page
Top Document: FAQ: Lisp Frequently Asked Questions 3/7 [Monthly posting]
Previous Document: [3-0] Why does (READ-FROM-STRING "foobar" :START 3) return FOOBAR instead of BAR?
Next Document: [3-2] Why can't I apply #'AND and #'OR?
[3-1] Why can't it deduce from (READ-FROM-STRING "foobar" :START 3) that the intent is to specify the START keyword parameter rather than
the EOF-ERROR-P and EOF-VALUE optional parameters?
In Common Lisp, keyword symbols are first-class data objects. Therefore,
they are perfectly valid values for optional parameters to functions.
There are only four functions in Common Lisp that have both optional and
keyword parameters (they are PARSE-NAMESTRING, READ-FROM-STRING,
WRITE-LINE, and WRITE-STRING), so it's probably not worth adding a
nonorthogonal kludge to the language just to make these functions slightly
less confusing; unfortunately, it's also not worth an incompatible change
to the language to redefine those functions to use only keyword arguments.
Top Document: FAQ: Lisp Frequently Asked Questions 3/7 [Monthly posting]
Previous Document: [3-0] Why does (READ-FROM-STRING "foobar" :START 3) return FOOBAR instead of BAR?
Next Document: [3-2] Why can't I apply #'AND and #'OR?
Part1 - Part2 - Part3 - Part4 - Part5 - Part6 - Part7 - Single Page
[ Usenet FAQs | Search | Web FAQs | Documents | RFC Index ]
Send corrections/additions to the FAQ Maintainer:
ai+lisp-faq@cs.cmu.edu
Last Update July 24 2008 @ 00:14 AM