On Sun, 14 Apr 1996, Billy H. Chan (~{3B:FH;~}) wrote:
> My solution, and it's semi-wasteful, was to preallocate all that memory.
> Let each zone have it's full x00 rooms (using dummy rooms for those that
> aren't currently in use). Thus, no memory problems or renumbering
> problems.
> Of course, if memory is tight, this won't help a bit, but at least for the
> Menudriven olc by Levork(wonder if it's still avail at cambot), it avoided
> many problems.
> Plus, most builders seem to have no problems filling all 100 rooms out.
I think I've knowon too many builders who write a couple of rooms then
don't show up for a while. Of course, the real memory hogs in circle are
all the descriptions, so if those are null or short you're really not
using that much extra memory.
The next version of obuild which I'm working on will continue to use the
implementor-specified number of prototype slots as in previous versions
but I'm changing the real_room etc routines to use a binary search and if
unsuccessful search the extra prototypes created by the olc (idea
courtesy Johan Eenfeldt :) ). That'll solve the problem of slow lookups.
Sam
This archive was generated by hypermail 2b30 : 12/18/00 PST