home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.windows.x
- Path: sparky!uunet!charon.amdahl.com!pacbell.com!ames!elroy.jpl.nasa.gov!llyene!thyme!kaleb
- From: kaleb@thyme.jpl.nasa.gov (Kaleb Keithley)
- Subject: Re: FLAME, FLAME ON X!!!
- Message-ID: <1992Nov18.170444.29009@thyme.jpl.nasa.gov>
- Organization: Jet Propulsion Laboratory, Pasadena, CA
- References: <1992Nov11.152545.1929@westford.ccur.com> <1ebp5cINNp7c@armory.centerline.com>
- Date: Wed, 18 Nov 92 17:04:44 GMT
- Lines: 21
-
- In article jimf@centerline.com (Jim Frost) writes:
- >>>Actually, I once saw a malloc package that could be made to return some
- >>>memory to the operating system by clever use of sbrk and brk, but I doubt
- >
- >I've written such a thing, actually. It's not particularly difficult
- >although it becomes a question of whether it's smarter to do the
- >correct brk/sbrk or to hang onto the piece (the brk/sbrk requires a
- >system call which you'd prefer to avoid). I dealt with that issue by
- >never doing a negative sbrk unless I had the whole piece that I got
- >when I did the positive sbrk, but a threshold is probably a better
- >approach.
- >
-
- But all the world's not a Sun. I've had people tell me that a negative
- value to sbrk on other systems either is ignored or is an error.
-
- --
-
- Kaleb Keithley kaleb@thyme.jpl.nasa.gov
-
- Not authorized, in any way, shape, or form, to speak for anyone.
-