Commit graph

6 commits

Author SHA1 Message Date
martti
e69ab8c365 COMMENT should start with a capital letter. 2003-07-21 16:35:12 +00:00
wiz
04f62f706a Change address of maintainer per PR 22170. 2003-07-19 08:54:23 +00:00
jmmv
0916498c1b Place WRKSRC where it belongs, to make pkglint happy; ok'ed by wiz. 2003-03-29 12:40:00 +00:00
wiz
e1e2ff0628 Replace collver@linuxfreemail.com with collver1@attbi.com.
Closes PRs 19516, 19517, 19518, 19519, 19520, 19521, 19522, 19523,
19524, 19525 and some more, perhaps.
2002-12-24 18:55:32 +00:00
zuntum
c72c1cf5f9 Move pkg/ files into package's toplevel directory 2001-11-01 00:57:41 +00:00
agc
00251c6491 Initial import of libmemmgr-1.04 into the packages collection.
Provided in PR 12581 by Ben Collver (collver@linuxfreemail.com)

MemMgr is a fairly trivial memory management library.  There
is little it does that cannot be done using routines in  the
C library.  (In fact, allocation and disposal is implemented
using C library routines.)  The purposes of MemMgr are  two-
fold.

(i)  Minimize  configuration  burden  on  applications  that
     dynamically allocate memory.  For instance, malloc() on
     some  systems  returns  a  char  pointer;  on others it
     returns a void pointer.  The  MemMgr  library  routines
     encapsulate  system-specific  configuration differences
     and exports a fixed interface which is  system-indepen-
     dent.  Once you compile and install it, you just use it
     without thinking about whether your UNIX is System V or
     BSD inspired.

(ii) Provide  two parallel sets of allocation routines which
     either return NULL  (for  applications  which  want  to
     check)  or panic (for applications which simply want to
     die) on allocation failures.  Panicking is  implemented
     using the ETM library, which introduces a dependency on
     the ETM distribution.  So be it.  I use ETM for all  my
     programs anyway
2001-04-27 12:10:40 +00:00