Mailing-List: contact zsh-workers-help@zsh.org; run by ezmlm
Precedence: bulk
From: Bart Schaefer <schaefer@brasslantern.com>
Message-Id: <160214135247.ZM3326@torch.brasslantern.com>
Date: Sun, 14 Feb 2016 13:52:47 -0800
In-Reply-To: <20160205222750.1fda3574@ntlworld.com>
Comments: In reply to Peter Stephenson <p.w.stephenson@ntlworld.com>
        "Re: PATCH: funcstack[-1]  (formerly Suppress tracing of "set +x")" (Feb  5, 10:27pm)
References: <20151230104531.GA20496@linux.vnet.ibm.com> 
	<5683F898.7010907@inlv.org> 
	<20160205100902.GA14979@linux.vnet.ibm.com> 
	<20160205102735.1f09973a@pwslap01u.europe.root.pri> 
	<20160205104444.2437ad33@pwslap01u.europe.root.pri> 
	<20160205160236.1274aa5b@pwslap01u.europe.root.pri> 
	<20160205222750.1fda3574@ntlworld.com>
To: Zsh hackers list <zsh-workers@zsh.org>
Subject: Assigning to $0 (formerly: PATCH: funcstack[-1])
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii

On Feb 5, 10:27pm, Peter Stephenson wrote:
}
} By the way, looking at the code I just notice that the following isn't
} an error even though it doesn't do what you presumably expect:
} 
} % setopt posixargzero
} % print $0
} zsh
} % 0=foo
} % print $0
} zsh
} 
} Maybe that's OK so far, but you don't even get the value back when you
} unset the option; it's silently lost.

So what behavior would be preferable?

1. POSIXARGZERO makes $0 report an error on assignment (read only?)

2. the value is stored and reappears when POSIXZERO is unset?

3. as (2) but a warning is printed?

As another by-the-way:

torch% print $0; () { typeset -g 0=argzero; print $0 }; print $0
Src/zsh
argzero
Src/zsh

So typeset will accept 0 as a valid name and -g as a valid option, but
can't actually set the global $0.