Re: I-D ACTION:draft-daboo-sieve-include-03.txt (fwd)

"Aaron Stone" <aaron@serendipity.cx> Tue, 30 August 2005 21:04 UTC

Received: from above.proper.com (localhost.vpnc.org [127.0.0.1]) by above.proper.com (8.12.11/8.12.9) with ESMTP id j7UL4Ym8013289; Tue, 30 Aug 2005 14:04:34 -0700 (PDT) (envelope-from owner-ietf-mta-filters@mail.imc.org)
Received: (from majordom@localhost) by above.proper.com (8.12.11/8.12.9/Submit) id j7UL4YcV013288; Tue, 30 Aug 2005 14:04:34 -0700 (PDT)
X-Authentication-Warning: above.proper.com: majordom set sender to owner-ietf-mta-filters@mail.imc.org using -f
Received: from lucite.serendipity.cx (IDENT:c9ckd9587go5xbspm8pr@serendipity.palo-alto.ca.us [66.92.2.88] (may be forged)) by above.proper.com (8.12.11/8.12.9) with ESMTP id j7UL4YEc013281 for <ietf-mta-filters@imc.org>; Tue, 30 Aug 2005 14:04:34 -0700 (PDT) (envelope-from aaron@serendipity.cx)
Received: by lucite.serendipity.cx (Postfix, from userid 1003) id 9A7F96023A26; Tue, 30 Aug 2005 14:03:34 -0700 (PDT)
Received: from serendipity.palo-alto.ca.us (localhost [127.0.0.1]) by lucite.serendipity.cx (Postfix) with SMTP id D5D3B6023EA3; Tue, 30 Aug 2005 14:03:30 -0700 (PDT)
Date: Tue, 30 Aug 2005 21:03:30 -0000
To: Nigel Swinson <Nigel.Swinson@rockliffe.com>
Subject: Re: I-D ACTION:draft-daboo-sieve-include-03.txt (fwd)
From: Aaron Stone <aaron@serendipity.cx>
X-Mailer: TWIG 2.8.2
Message-ID: <twig.1125435810.82298@serendipity.palo-alto.ca.us>
In-Reply-To: <00e501c5ad87$f8987b60$662c2a0a@rockliffe.com>
References: <twig.1125014327.8763@serendipity.palo-alto.ca.us> , <twig.1125014327.8763@serendipity.palo-alto.ca.us> <twig.1125020754.94965@serendipity.palo-alto.ca.us> <1125054534.15136.180.camel@chico.njus.no> <005c01c5aa44$49f18430$cf0ac050@nigelhome> <1125069059.15136.206.camel@chico.njus.no>, <1125069059.15136.206.camel@chico.njus.no> <twig.1125083963.7536@serendipity.palo-alto.ca.us> <028101c5ac9a$342ccee0$dbfac350@nigelhome> <4314936A.2060903@isode.com>
Cc: Sieve Mailing List <ietf-mta-filters@imc.org>
X-DSPAM-Result: Innocent
X-DSPAM-Confidence: 0.6000
X-DSPAM-Probability: 0.0000
X-DSPAM-Signature: !DSPAM:4314c9a6133149662536611!
Sender: owner-ietf-mta-filters@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-mta-filters/mail-archive/>
List-ID: <ietf-mta-filters.imc.org>
List-Unsubscribe: <mailto:ietf-mta-filters-request@imc.org?body=unsubscribe>

On Tue, Aug 30, 2005, ""Nigel Swinson"" <Nigel.Swinson@rockliffe.com>
said:

>> I think we all agree what the term "global variable" means in the 
>> variables draft.
>> But if people feel that the term "global variable" might be confusing, we 
>> can still replace it with something else as an editorial change.
> 
> Well at the risk of getting hit, I think it would be wise to change it from:
> 
>    All variables have global scope: they are visible until processing
>    stops.
> 
> To:
> 
>    All variables have file scope: they are visible to the remainder
>    of the current script.

As Kjetil pointed out last week, there is only one script, though there
may be many files included. We should be careful not to confuzzle the two
words. Also, from the point of view of the variables draft in a vacuum,
there is only one file, only one script, and only one scope. 

How about this:

    All variables have global scope within a script. Future specifications
    may allow for a script to be composed of more than one file, or for
    running more than one script per message [delivery?]. Such
    specifications may provide for different variable scoping rules.

Aaron