aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
-rw-r--r--doc/lispref/control.texi10
1 files changed, 5 insertions, 5 deletions
diff --git a/doc/lispref/control.texi b/doc/lispref/control.texi
index b0cd777bead..33051a6de51 100644
--- a/doc/lispref/control.texi
+++ b/doc/lispref/control.texi
@@ -419,13 +419,13 @@ This is not completely equivalent because it can evaluate @var{arg1} or
419@cindex pcase 419@cindex pcase
420@cindex pattern matching 420@cindex pattern matching
421 421
422@c Issue: I use ‘case’ w/ the thought that it being an alias
423@c to ‘cl-case’ is an ``implementation detail''.
424@c Is this okay?
425Aside from the four basic conditional forms, Emacs Lisp also 422Aside from the four basic conditional forms, Emacs Lisp also
426has a pattern-matching conditional form, the @code{pcase} macro, 423has a pattern-matching conditional form, the @code{pcase} macro,
427a hybrid of @code{cond} and @code{case} 424a hybrid of @code{cond} and @code{case}
428that overcomes their limitations. 425(@pxref{Conditionals,,,cl,Common Lisp Extensions})
426that overcomes their limitations and introduces
427the @dfn{pattern matching} programming style.
428First, the limitations:
429 429
430@itemize 430@itemize
431@item The @code{cond} form chooses among alternatives 431@item The @code{cond} form chooses among alternatives
@@ -442,7 +442,7 @@ For that, why not use @code{case}?
442@item 442@item
443The @code{case} macro chooses among alternatives by evaluating 443The @code{case} macro chooses among alternatives by evaluating
444the equality of its first argument against a set of specific 444the equality of its first argument against a set of specific
445values (@pxref{Conditionals,,,cl,Common Lisp Extensions}). 445values.
446The limitations are two-fold: 446The limitations are two-fold:
447 447
448@enumerate 448@enumerate