Re: malloc() vs. mymalloc()

• Date: Mon, 1 Apr 1996 10:46:46 PST
• From:
  Pavel Curtis <pavel@parc.xerox.com>
• Cc: moo-cows@parc.xerox.com
• In-reply-to: Christopher Unkel's message of "Sun, 31 Mar 1996 18:23:03 PST" <Pine.SUN.3.91.960331211501.19245B-100000@ren.us.itd.umich.edu>

Christopher Unkel writes:
> Is there a reason that timers.c and regexp.c call malloc() and free() 
> directly, instead of calling mymalloc() and myfree()?  pattern.c uses 
> mymalloc() but can't seem to decide between free() or myfree()...

The timers module is almost completely separable from the rest of the server,
so I used malloc() to keep it so, in case I (or anyone else) wanted to use it
again in some other context.

In pattern.c, I use myfree() for anything allocated by mymalloc() and free()
for anything allocated by the (externally developed) regexp package, which uses
malloc() to allocate things.

	Pavel

• malloc() vs. mymalloc()
• From: Christopher Unkel <cunkel@us.itd.umich.edu>

• Prev: malloc() vs. mymalloc()
• Next: Memory Usage of MOOs
• Index: MOO-cows
• Thread: MOO-cows