Received: from mail.proteosys.com ([213.139.130.197]) by nummer-3.proteosys with Microsoft SMTPSVC(6.0.3790.3959);
	 Wed, 10 Sep 2008 17:39:34 +0200
Received: by mail.proteosys.com (8.13.8/8.13.8) with ESMTP id m8AFdQIe015245
	for <rainer.schoepf@PROTEOSYS.COM>; Wed, 10 Sep 2008 17:39:27 +0200
Received: from listserv.uni-heidelberg.de (listserv.uni-heidelberg.de [129.206.100.94])
	by relay.uni-heidelberg.de (8.14.1/8.14.1) with ESMTP id m8AFWO53014361
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);
	Wed, 10 Sep 2008 17:32:25 +0200
Received: from listserv.uni-heidelberg.de (localhost.localdomain [127.0.0.1])
	by listserv.uni-heidelberg.de (8.13.1/8.13.1) with ESMTP id m89M1PPo032197;
	Wed, 10 Sep 2008 17:32:17 +0200
Received: by LISTSERV.UNI-HEIDELBERG.DE (LISTSERV-TCP/IP release 15.5) with
          spool id 32531 for LATEX-L@LISTSERV.UNI-HEIDELBERG.DE; Wed, 10 Sep
          2008 17:32:16 +0200
Received: from relay.uni-heidelberg.de (relay.uni-heidelberg.de
          [129.206.100.212]) by listserv.uni-heidelberg.de (8.13.1/8.13.1) with
          ESMTP id m8AFWGD1020635 for <LATEX-L@listserv.uni-heidelberg.de>;
          Wed, 10 Sep 2008 17:32:16 +0200
Received: from rv-out-0708.google.com (rv-out-0708.google.com [209.85.198.241])
          by relay.uni-heidelberg.de (8.14.1/8.14.1) with ESMTP id
          m8AFWCOG013973 for <LATEX-L@listserv.uni-heidelberg.de>; Wed, 10 Sep
          2008 17:32:15 +0200
Received: by rv-out-0708.google.com with SMTP id c5so2258422rvf.10 for
          <LATEX-L@listserv.uni-heidelberg.de>; Wed, 10 Sep 2008 08:32:11 -0700
          (PDT)
Received: by 10.141.23.7 with SMTP id a7mr907645rvj.58.1221060731288; Wed, 10
          Sep 2008 08:32:11 -0700 (PDT)
Received: from ?10.0.1.102? ( [219.90.231.17]) by mx.google.com with ESMTPS id
          g22sm12370853rvb.8.2008.09.10.08.32.09 (version=TLSv1/SSLv3
          cipher=RC4-MD5); Wed, 10 Sep 2008 08:32:10 -0700 (PDT)
Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Apple Message framework v928.1)
X-Mailer: Apple Mail (2.928.1)
X-Spam-Whitelist: <wspr81@gmail.com>
Message-ID:  <3C149193-F7ED-45F3-A683-29BF0687BE19@gmail.com>
Date:         Thu, 11 Sep 2008 01:02:06 +0930
Reply-To: Mailing list for the LaTeX3 project
              <LATEX-L@LISTSERV.UNI-HEIDELBERG.DE>
Sender: Mailing list for the LaTeX3 project <LATEX-L@LISTSERV.UNI-HEIDELBERG.DE>
From: Will Robertson <wspr81@GMAIL.COM>
Subject: Improvements to the syntax markup of source3
To: LATEX-L@LISTSERV.UNI-HEIDELBERG.DE
Precedence: list
List-Help: <http://listserv.uni-heidelberg.de/cgi-bin/wa?LIST=LATEX-L>,
           <mailto:LISTSERV@LISTSERV.UNI-HEIDELBERG.DE?body=INFO%20LATEX-L>
List-Unsubscribe: <mailto:LATEX-L-unsubscribe-request@LISTSERV.UNI-HEIDELBERG.DE>
List-Subscribe: <mailto:LATEX-L-subscribe-request@LISTSERV.UNI-HEIDELBERG.DE>
List-Owner: <mailto:LATEX-L-request@LISTSERV.UNI-HEIDELBERG.DE>
List-Archive: <http://listserv.uni-heidelberg.de/cgi-bin/wa?LIST=LATEX-L>
X-ProteoSys-SPAM-Score: -2.599 () BAYES_00
X-Scanned-By: MIMEDefang 2.64 on 213.139.130.197
Return-Path: owner-latex-l@LISTSERV.UNI-HEIDELBERG.DE
X-OriginalArrivalTime: 10 Sep 2008 15:39:34.0215 (UTC) FILETIME=[6CA00D70:01C9135B]
Status: R
X-Status: 
X-Keywords:                  
X-UID: 5273

Hello,

I just did a bunch of regexps on the expl3 bundle to standardise the  
markup used to document the syntax for functions. So no more
   "{" <xyz> "}"
with varying amount of whitespace; it's now all
   \Arg{xyz}

Standardising strings like "true code", "cs", "arg", and so on would  
also be useful, but I haven't done that yet.

I'm been trying to think of a "better" way to do this documentation,  
since in many cases the syntax is identical or obvious from the  
function spec itself. I mean, writing
   \xyz_foo:nnTF
then
   "\xyz_foo:nnTF" \Arg{arg1} \Arg{arg2} \Arg{true code} \Arg{false  
code}
is rather redundant.

I don't have a good solution in mind, though.

If you've got any dormant thoughts about how the documentation of  
source3 could be improved, let's talk about it. Of course, actually  
adding in more words (and more commas from Chris) would certainly help  
a lot, too.

Will