summaryrefslogtreecommitdiffstats
path: root/lib/libc/stdlib/getenv.3
Commit message (Collapse)AuthorAgeFilesLines
* Back out all POSIXified *env() changes.ache2007-05-011-35/+18
| | | | | | | | | 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 .Ddache2007-04-301-1/+1
| | | | Suggested by: Henrik Brix Andersen <henrik@brixandersen.dk>
* Add phraseache2007-04-301-1/+2
| | | | | "so altering the argument shall change the environment." into putenv description.
* Make putenv() fully conforms to Open Group specs Issue 6ache2007-04-301-6/+13
| | | | | | | | | | | (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 "forache2007-04-301-5/+0
| | | | | | | | | 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"
* Make setenv, putenv, getenv and unsetenv conforming to Open Group specsache2007-04-301-9/+23
| | | | | | | | | Issue 6 (also IEEE Std 1003.1-2001) in following areas: args, return, errors. Putenv still needs rewriting because specs explicitly says that altering passed string later should change the environment (currently we copy the string so can't provide that).
* Per Regents of the University of Calfornia letter, remove advertisingimp2007-01-091-4/+0
| | | | | | clause. # If I've done so improperly on a file, please let me know.
* Note that the value from getenv() should not be modified by applications.trhodes2006-10-121-1/+5
| | | | | PR: 60544 Reviewed by: ru
* getenv.3: Put "is" on a line with other wordstrhodes2006-10-071-2/+1
| | | | | | | | getobjformat.3: "takes precedence over" is not an envrionment variable. PR: 75545 Submitted by: n-kogane@syd.odn.ne.jp MFC after: 3 days
* Sort sections.ru2005-01-201-11/+11
|
* mdoc(7) fixes.ru2004-07-071-2/+3
|
* Move the return value information about the getenv(3) library functionhmp2004-07-061-4/+10
| | | | | | | | | under the RETURN VALUES section so it is consistent with others. Cleanup the return value text for getenv(3) a little while I am here. PR: docs/58033 MFC after: 3 days
* Mechanically kill hard sentence breaks.ru2004-07-021-2/+4
|
* mdoc(7) police: Fixed abuses of the .Ar and .Em macros.ru2002-12-181-13/+14
|
* Move to using .In instead of .Fd #include <> for include mark-up.asmodai2001-09-071-1/+1
| | | | Inspired by comment from: dd
* Use ``.Rv -std'' wherever possible.ru2001-08-311-8/+1
| | | | Submitted by: yar
* Remove whitespace at EOL.dd2001-07-151-1/+1
|
* .St -ansiC -> .St -isoCru2001-02-261-1/+1
|
* mdoc(7) police: split punctuation characters + misc fixes.ru2001-02-011-1/+1
|
* Use Fx macro wherever possible.ru2000-11-141-1/+3
|
* Use `Er' variable to define first column width in ERRORS section.phantom2000-05-061-1/+1
|
* Introduce ".Lb" macro to libc manpages.phantom2000-04-211-0/+2
| | | | More libraries manpages updates following.
* Document the memory leak that is inherent in FreeBSD's semanticsarchie2000-01-261-0/+15
| | | | | | for getenv()/putenv(). PR: 10341 5604
* $Id$ -> $FreeBSD$peter1999-08-281-1/+1
|
* Add $Id$, to make it simpler for members of the translation teams tonik1999-07-121-0/+1
| | | | | | | | | | | | | | | | | track. The $Id$ line is normally at the bottom of the main comment block in the man page, separated from the rest of the manpage by an empty comment, like so; .\" $Id$ .\" If the immediately preceding comment is a @(#) format ID marker than the the $Id$ will line up underneath it with no intervening blank lines. Otherwise, an additional blank line is inserted. Approved by: bde
* BSD 4.4 Lite Lib Sourcesrgrimes1994-05-271-0/+151
OpenPOWER on IntegriCloud