Typo
git-svn-id: svn://bknr.net/svn/trunk/thirdparty/cl-ppcre@4620 4281704c-cde7-0310-8518-8e2dc76b1ff0
This commit is contained in:
4
api.lisp
4
api.lisp
@ -1224,8 +1224,8 @@ sections. These sections may nest."
|
||||
(let* ((*use-bmh-matchers* nil)
|
||||
(comment-scanner (create-scanner "(?s)\\(\\?#.*?\\)"))
|
||||
(extended-comment-scanner (create-scanner "(?m:#.*?$)|(?s:\\(\\?#.*?\\))"))
|
||||
(quote-token-scanner "\\\\[QE]")
|
||||
(quote-token-replace-scanner "\\\\([QE])"))
|
||||
(quote-token-scanner (create-scanner "\\\\[QE]"))
|
||||
(quote-token-replace-scanner (create-scanner "\\\\([QE])")))
|
||||
(defun clean-comments (string &optional extended-mode)
|
||||
"Clean \(?#...) comments within STRING for quoting, i.e. convert
|
||||
\\Q to Q and \\E to E. If EXTENDED-MODE is true, also clean
|
||||
|
||||
@ -2052,7 +2052,7 @@ read.
|
||||
<ul>
|
||||
<li>A lot of hackers (especially users of Perl and other scripting
|
||||
languages) think that regular expressions are the greatest thing
|
||||
since slice bread and use it for almost everything. That is just
|
||||
since sliced bread and use it for almost everything. That is just
|
||||
plain wrong. Other hackers (especially Lispers) tend to think that
|
||||
regular expressions are the work of the devil and try to avoid them
|
||||
at all cost. That's also wrong. Regular expressions are a handy
|
||||
|
||||
Reference in New Issue
Block a user