Commit Graph

8144 Commits

Author SHA1 Message Date
jruoho
0fb5e18e02 Update the -- now quite big -- list of unsupported Linux options. 2010-05-04 06:13:43 +00:00
jruoho
26a87898ae Fix previous commit by also moving the type of _malloc_options. In addition,
add a (commented) note that _malloc_message should be documented better.
2010-05-03 08:23:20 +00:00
jruoho
60d71be703 Move the '_malloc_options' variable from malloc(3) to jemalloc(3). 2010-05-03 08:11:57 +00:00
jruoho
49bb3cb02e Note the problems with SSP. 2010-05-03 06:11:38 +00:00
jruoho
40c884b1c3 Note secure_path(3) in SEE ALSO. 2010-05-03 05:53:56 +00:00
jruoho
ef40c024f6 Move the examples to where they belong, in EXAMPLES. 2010-05-03 05:11:34 +00:00
jruoho
26e9ae259a Split the implementation details of malloc(3) to a separate jemalloc(3)
manual page. This way malloc(3) can follow the standard terse format used
elsewhere in the libc, while additional details can be added to jemalloc(3).

Note HISTORY and AUTHORS in jemalloc(3), and add some reading material to
SEE ALSO.
2010-05-03 05:01:53 +00:00
jruoho
a80a543b80 Add more markup. 2010-05-03 03:47:51 +00:00
jruoho
280488d6bc Note that the return type sould arguably be intmax_t instead of long long. 2010-05-01 08:35:52 +00:00
jruoho
061351141b Remove the (incorrect) note about inconsistent return values. Name the exit
code as EXIT_FAILURE instead of integer 1.
2010-05-01 08:30:00 +00:00
jruoho
413ef23a32 Add more bugs. Namely, besides the return values that are confusing, no
function in a modern standard C library, exposed by <stdlib.h>, should be as
easy to (buffer) overflow as strsuftollx(3).

In addition, improvements to wording and markup.
2010-05-01 08:12:30 +00:00
jruoho
4519228649 Improvements to wording and markup.
In addition, list more bugs and caveats. Namely, the NetBSD implementation
(like the FreeBSD one where this was ported to) requires that the comparison
keys are allocated dynamically, and that hdestroy() will try to free(3) each
key. This obviously severely limits the portability, given that other
implementations (for example, the Linux one) make no such assumptions. Both
approaches are legitimate, and thus the real bug is in the ambiguity of the
standard.
2010-05-01 06:18:03 +00:00
jruoho
a293ac8fcc Rewrite the HISTORY section. 2010-04-30 10:24:02 +00:00
jruoho
eecb0b5e2c Put the period outside the quotation marks. 2010-04-30 10:09:23 +00:00
jruoho
cb375ee477 Add STANDARDS and CAVEATS. The latter notes the ambiguity of tdelete() when
deleting the root node.
2010-04-30 10:06:52 +00:00
jruoho
68cb312101 Remove the note about eaccess(); no such thing in NetBSD. 2010-04-30 09:41:59 +00:00
jruoho
42e4725801 Also: in the example EOVERFLOW is probably better than ENOMEM. 2010-04-30 07:16:35 +00:00
jruoho
67e69a6bf8 As err(3) instructs, use EXIT_FAILURE in the example. 2010-04-30 07:14:15 +00:00
jruoho
75d4d306c5 Steal the "malloc() vs. calloc()" -idiom from the OpenBSD's malloc(3).
While it may be debated how useful this is, good idiomatic usage examples
are exactly the kind of thing one would hope to see more in manual pages.
2010-04-30 07:00:51 +00:00
wiz
779fbbb100 Wording. 2010-04-30 06:54:16 +00:00
wiz
5a5627574d Sort errors. 2010-04-30 06:51:52 +00:00
wiz
0264ec21bd Merge two entries for the same error. 2010-04-30 06:48:20 +00:00
jruoho
54f0f8584b Use a SECURITY CONSIDERATIONS instead of the BUGS section, and steal this
section from FreeBSD (with minor modifications).
2010-04-30 06:34:23 +00:00
jruoho
1ad0e6c25b Put SECURITY CONSIDERATIONS as the last section. 2010-04-30 06:23:56 +00:00
jruoho
2f941c83c7 Fix the mess in the sections; someone went to sleep in the middle of a
sentence...
2010-04-30 06:22:28 +00:00
jruoho
b0e9ddf609 They've finally made gets(3) obsolete (in POSIX, at least). 2010-04-30 06:00:14 +00:00
jruoho
1b80a21f09 Add HISTORY. 2010-04-30 05:56:14 +00:00
jruoho
fba71b9825 Marked as legacy already in SUSv2; removed in POSIX 2001. 2010-04-30 05:50:46 +00:00
jruoho
d307542670 Deprecated in POSIX (rev. 2008). 2010-04-30 05:09:23 +00:00
jruoho
4078f3e9d1 Also tmpnam(3) and tempnam(3) are now obsolete in POSIX. 2010-04-30 04:55:10 +00:00
jruoho
92370ee67d Interestingly, the committees plan to remove also isascii(3) and toascii(3)
in the future.
2010-04-30 04:46:18 +00:00
jruoho
70d2311835 More obsolete things. These are all already deprecated in NetBSD, but it is
worth noting that also the standard has marked these as legacy.
2010-04-30 04:39:16 +00:00
jruoho
a2ebffc113 Reference timeradd(3). 2010-04-30 04:17:45 +00:00
jruoho
eccc1c42e1 Add STANDARDS section. Note that both functions were marked as obsolescent
in POSIX (2008); "timer_gettime(2) and timer_settime(2) should be used".
2010-04-30 04:15:49 +00:00
jruoho
71a03dd7f6 Small improvements to wording and markup. 2010-04-30 04:06:20 +00:00
jruoho
c6d218be32 .Nm -> .Fn. 2010-04-30 03:52:13 +00:00
jruoho
ec4fdaa41e It was nice to expect fts(3) to appear in the '88 revision. But perhaps
people had too high hopes.
2010-04-29 17:39:03 +00:00
jruoho
934551e44a No more usleep(3) in POSIX; "use nanosleep(2) instead". 2010-04-29 17:29:56 +00:00
jruoho
6adec4717c Fix markup. 2010-04-29 17:17:18 +00:00
jruoho
3d0a5d8f1c Note that also POSIX has deprecated utime(3). 2010-04-29 17:07:00 +00:00
jruoho
648a1295d8 Fix the standards: utimes(2) is still in SUSv4, although marked as legacy. 2010-04-29 17:02:38 +00:00
jruoho
61564b38a1 Note the ambiguity of the return value in the BUGS section.
From Christian Biere <christianbiere@gmx.de> in PR #39392.
2010-04-29 10:03:12 +00:00
jruoho
c25207d763 Note POSIX compliance. 2010-04-29 08:06:21 +00:00
wiz
0c57838d7b Sort errors. 2010-04-29 07:31:02 +00:00
wiz
3292536e4b Add punctuation. 2010-04-29 07:27:30 +00:00
wiz
a917229f2a Improve a sentence. 2010-04-29 07:26:39 +00:00
jruoho
c792ab3e8e Note that utimes(2) no longer enjoys the blessing of POSIX. 2010-04-29 07:14:35 +00:00
jruoho
157d0c3eea Add some STANDARDS lingo, mainly to note the functions that have been
removed from POSIX (2008).
2010-04-29 06:54:26 +00:00
jruoho
c329b28a22 Properly mark the standard that "deprecated" all of these. 2010-04-29 06:07:35 +00:00
jruoho
8cd9bb9479 Note the recent changes. 2010-04-29 05:42:04 +00:00