Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 12.0 \(3445.100.39\))
References: <AB0F488B-AD43-44CC-B519-58E742E0D2E7@gmail.com>
            <ECA49231-1A06-491A-9ED2-D23B6722A8DA@wspr.io>
Message-ID:  <189D41EC-96F9-4F35-8248-81A18641C97C@gmail.com>
Date:         Wed, 3 Oct 2018 18:37:48 +0200
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:         Johannes Burtscher <j.burtscher@GMAIL.COM>
Subject: Re: Function arguments vs "global" variables
To:           LATEX-L@LISTSERV.UNI-HEIDELBERG.DE
In-Reply-To:  <ECA49231-1A06-491A-9ED2-D23B6722A8DA@wspr.io>
Precedence: list
Envelope-To: <rainer.schoepf@GMX.NET>
Content-Transfer-Encoding: 8bit
Status: R

Hi Will,

> In my own code I think it comes down to scope. If you’re operating on variables that are broader in scope than the auxiliary functions you’re using to process them, I wouldn’t use arguments. 

That’s pretty interesting - I’ve only been toying around with single code snippets and never thought about it in this way. I think I’ll give that (along with “showing intent”) simply a try and already look forward to the first round of refactoring… :)

Thanks
Johannes