[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: The poor state of documentation of pcase like things.

From: Eli Zaretskii
Subject: Re: The poor state of documentation of pcase like things.
Date: Sat, 19 Dec 2015 22:58:50 +0200

> From: address@hidden (Phillip Lord)
> Cc: David Kastrup <address@hidden>,  <address@hidden>,  <address@hidden>
> Date: Sat, 19 Dec 2015 20:35:14 +0000
> Eli Zaretskii <address@hidden> writes:
> >> 
> >>     Conditionals
> >> 
> >>     * Pattern matching case statement::  How to use @code{pcase}.
> >> 
> >>     Nonlocal Exits
> >> 
> >>     * Catch and Throw::         Nonlocal exits for the program's own 
> >> purposes.
> >>     * Examples of Catch::       Showing how such nonlocal exits can be 
> >> written.
> >>     * Errors::                  How errors are signaled and handled.
> >>     * Cleanups::                Arranging to run a cleanup form if an
> >> 
> >> Note that "Conditionals" now appears twice: as a proper node name and as
> >> a newly added section containing only "pcase" and nothing else.
> >
> > Yes, and that is a problem because...?
> I would think that it would make more sense to have "Pattern Matching"
> at top-level. pcase is conditional, but neither pcase-let nor
> pcase-lambda really is. The "conditional" can have a short section
> saying "pcase is like case but with pattern matching", as can the "let"
> and "lambda" documentation.

Sorry, I'm not following.  If we think the second instance of
"Conditionals" is not the best text, we can change it at will.  Only
the first one must me identical to the node name.  The second one is
"Conditionals" because it was produced by a program and I left it
unchanged, but it can be changed if we want to.

reply via email to

[Prev in Thread] Current Thread [Next in Thread]