[latex3-commits] [l3svn] 02/02: Update style guide on nopar [ci skip]

noreply at latex-project.org noreply at latex-project.org
Mon Jun 13 23:41:46 CEST 2016

This is an automated email from the git hooks/post-receive script.

joseph pushed a commit to branch master
in repository l3svn.

commit 44049d0f97e1a929ddec166e1846719108bacd96
Author: Joseph Wright <joseph.wright at morningstar2.co.uk>
Date:   Mon Jun 13 22:34:38 2016 +0100

    Update style guide on nopar [ci skip]
 l3kernel/l3styleguide.tex |    7 +++++--
 1 file changed, 5 insertions(+), 2 deletions(-)

diff --git a/l3kernel/l3styleguide.tex b/l3kernel/l3styleguide.tex
index 690168a..fc476fd 100644
--- a/l3kernel/l3styleguide.tex
+++ b/l3kernel/l3styleguide.tex
@@ -1,6 +1,6 @@
 \iffalse meta-comment
-File l3styleguide.tex Copyright (C) 2011,2012,2015 The LaTeX3 Project
+File l3styleguide.tex Copyright (C) 2011,2012,2015,2016 The LaTeX3 Project
 It may be distributed and/or modified under the conditions of the
 LaTeX Project Public License (LPPL), either version 1.3c of this
@@ -158,7 +158,10 @@ look like the example:
 All code-level functions should be \enquote{long} if they accept any
 arguments, even if it seems \enquote{very unlikely} that a \cs{par} token
 will be passed. Thus \cs{cs_new_nopar:Npn} and so forth should only be used
-to create functions which accept no arguments at all.
+to create interfaces at the document level (where trapping \cs{par} tokens
+may be appropriate) or where comparison to other code known not to be
+\enquote{long} is required (\emph{e.g.}~when working with mixed
+\LaTeXe{}/\pkg{expl3} situations).
 The expandability of each function should be well-defined. Functions which
 cannot be fully expanded must be \texttt{protected}. This means that expandable

To stop receiving notification emails like this one, please contact
the administrator of this repository.

More information about the latex3-commits mailing list