From: Peter Stephenson <p.w.stephenson@ntlworld.com>
To: zsh-workers@sunsite.dk
Cc: "Sean C. Farley" <scf@FreeBSD.org>
Subject: Re: putenv()/environ bug
Date: Wed, 25 Jul 2007 21:53:21 +0100 [thread overview]
Message-ID: <20070725215321.00e3b110.p.w.stephenson@ntlworld.com> (raw)
In-Reply-To: <20070725093254.T20275@thor.farley.org>
On Wed, 25 Jul 2007 10:09:22 -0500 (CDT)
"Sean C. Farley" <scf@FreeBSD.org> wrote:
> As noticed here[1] following a change[2] in FreeBSD's *env() functions,
> zsh is mixing *env() (putenv() in this case) functions with direct
> access to the environ variable's contents against the IEEE Std 1003.1
> specification.
>
> BTW, is there a particular reason the standard *env() functions cannot
> be used for all operations to environ if found?
There's a long history of fiddling with these for problems on various
systems, so I'm a little unwilling to change it without some guidance.
For example,
/*
* Under Cygwin we must use putenv() to maintain consistency.
* Unfortunately, current version (1.1.2) copies argument and may
* silently reuse existing environment string. This tries to
* check for both cases
*/
This is a little confusing since the code in question (addenv in
params.c) doesn't actually use putenv().
Given we manipulate environ quite a lot anyway, is there any harm in
using only the zsh versions of zgetenv() and zputenv()? There's a
getenv() instead of a zgetenv() in init.c: I think that was just a typo
by me.
Index: Src/init.c
===================================================================
RCS file: /cvsroot/zsh/zsh/Src/init.c,v
retrieving revision 1.76
diff -u -r1.76 init.c
--- Src/init.c 6 Jul 2007 21:52:39 -0000 1.76
+++ Src/init.c 25 Jul 2007 20:53:06 -0000
@@ -832,7 +832,7 @@
if (emulation == EMULATE_ZSH)
ptr = home;
else
- ptr = getenv("HOME");
+ ptr = zgetenv("HOME");
if (ptr && ispwd(ptr))
pwd = ztrdup(ptr);
else if ((ptr = zgetenv("PWD")) && (strlen(ptr) < PATH_MAX) &&
--
Peter Stephenson <p.w.stephenson@ntlworld.com>
Web page now at http://homepage.ntlworld.com/p.w.stephenson/
next prev parent reply other threads:[~2007-07-25 20:54 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-25 15:09 Sean C. Farley
2007-07-25 20:53 ` Peter Stephenson [this message]
2007-07-26 0:14 ` Sean C. Farley
2007-07-28 18:46 ` Andrey Borzenkov
2007-07-29 19:08 ` Sean C. Farley
2007-07-30 20:39 ` Peter Stephenson
2007-07-30 20:52 ` Peter Stephenson
2007-07-30 22:44 ` Sean C. Farley
2007-07-31 9:00 ` Peter Stephenson
2007-07-31 18:09 ` Sean C. Farley
2007-07-30 22:39 ` Sean C. Farley
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20070725215321.00e3b110.p.w.stephenson@ntlworld.com \
--to=p.w.stephenson@ntlworld.com \
--cc=scf@FreeBSD.org \
--cc=zsh-workers@sunsite.dk \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/zsh/
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).