Yup, it sucks, but yah just gotta bite the bullet. plus, as you are going
through you get to see ALL the code. (every little bit) adding this stuff is a
great way to learn how this code really works. I also restructured a lot of the
functions that were running on if(this_thing) return; to be an if-else chain
with one release_buffer() at the end.
--Angus
______________________________ Forward Header __________________________________
Subject: Buffer Addon: Those silly release_buffer calls
Author: INTERNET:CIRCLE@POST.QUEENSU.CA at CSERVE
Date: 5/6/98 6:44 PM
The buffer system is all well and fine, I didn't have any difficulty
determining how it works or how to get it functional.
However, it has become time to add all the release_buffer calls and with
2798 get_buffer calls I find myself dreading the prospect. I cannot do them
a little at a time, as I can't place into production a mud that uses 180megs
of ram at startup before the buffers time out and it settles down to 10 megs
(which is a nice reduction from before I started adding the buffer system.)
--
-- Gary Barnett, MCNE http://www.ptialaska.net/~gbarnett/
-- Mallory@AntaresMUD telnet://antares.kaschynna.com:7000
--
+------------------------------------------------------------+
| Ensure that you have read the CircleMUD Mailing List FAQ: |
| http://democracy.queensu.ca/~fletcher/Circle/list-faq.html |
+------------------------------------------------------------+
This archive was generated by hypermail 2b30 : 12/15/00 PST