[26510] in Source-Commits
Re: /svn/athena r25590 - in trunk/debathena/debathena/dotfiles: . debian
daemon@ATHENA.MIT.EDU (Jonathan Reed)
Mon Jul 2 09:38:11 2012
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Jonathan Reed <jdreed@MIT.EDU>
In-Reply-To: <alpine.GSO.1.10.1207012358220.18441@multics.mit.edu>
Date: Mon, 2 Jul 2012 09:38:07 -0400
Cc: source-commits@MIT.EDU
Message-Id: <DEBBA34D-E64D-48A4-BC67-E08CA2542806@MIT.EDU>
To: Benjamin Kaduk <kaduk@MIT.EDU>
Content-Transfer-Encoding: 8bit
Ah, my bad. Yes, in fact, variable assignment does change the value, but as rewritten (with "set missing=0" before the echo/tr/grep), it's now fine.
-Jon
On Jul 1, 2012, at 11:59 PM, Benjamin Kaduk wrote:
> On Fri, 29 Jun 2012, Jonathan Reed wrote:
>
>>>
>>> Does variable assignment change $? ?
>>
>> $?foo is "is foo set". That's the same syntax for all the skip_foo variables. We tell people a variety of things, and in fact if you did set skip_sanity_checks=no-never-skip-them, this would trigger that code. "Don't do that.", but I can add the extra code and/or clean up the
>
> Sorry for the confusion; my remark was in tandem with the one about moving "missing=0" up a line -- if that variable assignment reset the value of "$?", then the conditional would fail.
>
> -Ben
>
>>
>>> The style would probably be better to move "missing=0" up one line, regardless.
>>
>> Sure.