Mailing-List: contact zsh-workers-help@zsh.org; run by ezmlm
Precedence: bulk
From: Bart Schaefer <schaefer@brasslantern.com>
Message-Id: <160508145807.ZM10454@torch.brasslantern.com>
Date: Sun, 8 May 2016 14:58:07 -0700
In-Reply-To: <20160508212858.384e3dbf@ntlworld.com>
Comments: In reply to Peter Stephenson <p.w.stephenson@ntlworld.com>
        "Re: leading '=' in enviroment variable truncated" (May  8,  9:28pm)
References: <CAEyFG7ZkxS9iuVtEoJT2aa_ErBm=Nm6JqkpSgt=-=3P-nuZBtg@mail.gmail.com> 
	<160508105949.ZM9904@torch.brasslantern.com> 
	<20160508201217.5924511a@ntlworld.com> 
	<160508132406.ZM10234@torch.brasslantern.com> 
	<20160508212858.384e3dbf@ntlworld.com>
To: zsh-workers@zsh.org
Subject: Re: leading '=' in enviroment variable truncated
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii

On May 8,  9:28pm, Peter Stephenson wrote:
} 
} On Sun, 8 May 2016 13:24:06 -0700
} Bart Schaefer <schaefer@brasslantern.com> wrote:
} > Astounding.
} > 
} > The Open Group spec for "setenv" explicitly prohibits "=" in the name,
} > and says nothing about the value.  The source code for setenv.c on
} > opensource.apple.com does nothing special with name or value.
} > 
} > How about this?
} 
} This tries to be smarter, but I don't know if it's worth it... it's
} untested on the target system.

If we're going to go so far as to have a configure test, shouldn't we
include a check that setenv is in fact defined before attempting to
run a test that uses it?