summaryrefslogtreecommitdiff
path: root/devel/libmemmgr
AgeCommit message (Collapse)AuthorFilesLines
2005-02-23Add RMD160 digests.agc1-1/+2
2004-01-20Move WRKSRC definition away from the first paragraph in a Makefile.agc1-2/+3
2003-12-24s/@netbsd.org/@NetBSD.org/ in MAINTAINER.jmmv1-2/+2
2003-12-13Update MAINTAINER email address.ben1-2/+2
2003-12-13Change from using packaged install program and flags, to a do-installben1-4/+5
target in pkgsrc, in order to have a better chance of installing on Solaris and other platforms.
2003-12-11Give these packages a higher chance to install on Solaris.ben1-2/+2
2003-12-11Update MASTER_SITES and HOMEPAGE to www.snake.net.ben1-3/+3
2003-07-21COMMENT should start with a capital letter.martti1-2/+2
2003-07-19Change address of maintainer per PR 22170.wiz1-2/+2
2003-03-29Place WRKSRC where it belongs, to make pkglint happy; ok'ed by wiz.jmmv1-3/+2
2002-12-24Replace collver@linuxfreemail.com with collver1@attbi.com.wiz1-2/+2
Closes PRs 19516, 19517, 19518, 19519, 19520, 19521, 19522, 19523, 19524, 19525 and some more, perhaps.
2001-11-01Move pkg/ files into package's toplevel directoryzuntum2-1/+1
2001-04-27Initial import of libmemmgr-1.04 into the packages collection.agc5-0/+119
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