src/lib/libc/stdlib/getenv.3, branch release/13.1.0

Renumber clauses to reduce diffs to other versions

2013-05-28T20:57:40Z

NetBSD, OpenBSD, and Android's Bionic number the clauses 1 through 3, so follow suit to make comparison easier.

General mdoc(7) and typo fixes.

2012-05-11T20:06:46Z

PR: 167734 Submitted by: Nobuyuki Koganemaru (kogane!jp.freebsd.org) MFC after: 3 days

Remove trailing whitespace per mdoc lint warning

2012-03-29T05:02:12Z

Disussed with: gavin No objection from: doc Approved by: joel MFC after: 3 days

Update the getenv(3) man page to reflect the recent change to the behavior

2009-12-06T23:51:27Z

of setenv(), putenv() and unsetenv() when dealing with corrupt entries in environ. They now output a warning and complete their task without error. MFC after: 1 week

Significantly reduce the memory leak as noted in BUGS section for

2007-07-04T00:00:41Z

setenv(3) by tracking the size of the memory allocated instead of using strlen() on the current value. Convert all calls to POSIX from historic BSD API: - unsetenv returns an int. - putenv takes a char * instead of const char *. - putenv no longer makes a copy of the input string. - errno is set appropriately for POSIX. Exceptions involve bad environ variable and internal initialization code. These both set errno to EFAULT. Several patches to base utilities to handle the POSIX changes from Andrey Chernov's previous commit. A few I re-wrote to use setenv() instead of putenv(). New regression module for tools/regression/environ to test these functions. It also can be used to test the performance. Bump __FreeBSD_version to 700050 due to API change. PR: kern/99826 Approved by: wes Approved by: re (kensmith)

Back out all POSIXified *env() changes.

2007-05-01T16:02:44Z

Not because I admit they are technically wrong and not because of bug reports (I receive nothing). But because I surprisingly meets so strong opposition and resistance so lost any desire to continue that. Anyone who interested in POSIX can dig out what changes and how through cvs diffs.

Bump .Dd

2007-04-30T19:37:10Z

Suggested by: Henrik Brix Andersen

Add phrase

2007-04-30T18:01:51Z

"so altering the argument shall change the environment." into putenv description.

Make putenv() fully conforms to Open Group specs Issue 6

2007-04-30T16:56:18Z

(also IEEE Std 1003.1-2001) The specs explicitly says that altering passed string should change the environment, i.e. putenv() directly puts its arg into environment (unlike setenv() which just copies it there). It means that putenv() can't be implemented via setenv() (like we have before) at all. Putenv() value lives (allows modifying) up to the next putenv() or setenv() call.

Remove special case skipping initial '=' of the setenv() value "for

2007-04-30T03:47:31Z

compatibility with the different environment conventions" (man page). With the standards, we don't have them different anymore and IEEE Std 1003.1-2001 says that "The values that the environment variables may be assigned are not restricted except that they are considered to end with a null byte"