[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: Sun, 20 Dec 2015 05:38:39 +0200

> From: address@hidden (Phillip Lord)
> Cc: <address@hidden>,  <address@hidden>,  <address@hidden>
> Date: Sat, 19 Dec 2015 22:23:54 +0000
> > 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.
> Simple change would be from:
> Conditionals
> * Pattern matching case statement::  How to use @code{pcase}.
> to
> Pattern Matching
> * Conditional::  How to use @code{pcase}

The last line can't be done, unless the node names are changed as
well.  Right now the pcase description is in the child node of
"Conditionals" whose name is "Pattern matching case statement".

Also, I think having 2 nodes named "Conditionals" and "Conditional"
will be too confusing.

> Pattern Matching
> (this would contain a generalised introduction and tutorial, based
> around pcase)
> * List Clauses::            Destructuring Lists
> * Predicates::              Matching with predicate functions
> * Booleans::                and and or
> * Guards::                  I don't quite understand guards
> * Conditionals::            pcase
> * Binding::                 pcase-let 
> * Lambda::                  pcase-lambda

These would be too short to justify a separate node, IMO.

> * New Patterns::            pcase-macro, with description of seq and map 
> support.

We avoid using "new" in manuals, because they are that only for one

reply via email to

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