MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
References: <AFA791BD-820C-4762-AF99-680B5A3DFA07@gmail.com>
            <4936E30A.5080209@morningstar2.co.uk>
            <87ljuxlybp.fsf@fawkes.hogwarts>
            <49370743.7050004@morningstar2.co.uk>
            <18745.37877.845526.230207@morse.mittelbach-online.de>
            <A9325DBA-A80E-4A6B-BE2B-B9FA4F005902@gmail.com>
            <18747.60665.106015.681211@morse.mittelbach-online.de>
            <944107A6-E45B-4F33-8F7B-AF98DC95AB54@gmail.com>
            <18748.52807.627728.138832@morse.mittelbach-online.de>
            <FF2C79FE-8C9A-43BC-98EA-794785F39861@gmail.com>
            <493D311A.1050906@morningstar2.co.uk>
Message-ID:  <18749.29915.27527.926725@morse.mittelbach-online.de>
Date:         Mon, 8 Dec 2008 20:26:19 +0100
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: Frank Mittelbach <frank.mittelbach@LATEX-PROJECT.ORG>
Subject: Re: expl3 "token list" terminology
To: LATEX-L@LISTSERV.UNI-HEIDELBERG.DE
In-Reply-To:  <493D311A.1050906@morningstar2.co.uk>
Precedence: list
Status: R

Joseph Wright writes:
 > Will Robertson wrote:
 > 
 > > While we're discussing terminology, is there any overarching reason that
 > > global and local variables have their scope as a prefix \g_ or \l_ ? (My
 > > reason for asking being that I would slightly prefer something like
 > > \module_name_l_tlp or something thereabouts, but I'm not really fussed.)
 > 
 > My thinking was that \l_<module>... makes it easy to see a variable in a
 > load of \<module> functions.

precisely, it is a very good indicator within the code and also if you look
for a variable then there is a single place (l_ for local g_ for global) in
the index to look, very useful in my experience. I wouldn't want to miss that.

it makes variables nicely separated from functions in both places

frank