Re: Generic OLC routines

From: Mark A. Heilpern (heilpern@MINDSPRING.COM)
Date: 11/06/97

How about replace_room(struct room_data *new, struct room_data *old)
etc. for mob/obj/zon/shop

Otherwise a remove_ followed by add_ has to be done.

At 07:13 PM 11/6/97 -0500, you wrote:
>I'm currently underway in creating generic OLC routines for CircleMUD which
>are simple to use and not geared toward any one system.
>I'm creating functions as such:
>add_room(struct room_data *)
>remove_room(int num, byte type) /* 3000, VIRTUAL and 3, REAL for example */
>add_obj(struct obj_data *)
>remove_obj(int num, byte type)
>save_mobs()     /* Interfaces undecided at the moment. */
>The functions are based quite a bit on the current OasisOLC routines as
>that is what I have been working with.
>If anyone has any feedback or suggestions (particularly Sammy so that this
>works well with his OLC system too, or maybe he already has some, I haven't
>looked in a while...) then please mail me.
>Improvements over the Oasis routines:
>No more creating a whole new database and freeing it! (Less fragmentation)
>Doesn't have to copy the whole database! (Faster)
>I've mailed my preliminary changes off for bpl13 and maybe in the future we
>can have something like this included so people do not have to create their
>own routines.  This will also minimize breakage if CircleMUD's world format
>changes... :)
>George Greer  -   | Genius may have its limitations, but
> | is not thus handicapped. -- Elbert Hubbard
>     +------------------------------------------------------------+
>     | Ensure that you have read the CircleMUD Mailing List FAQ:  |
>     | |
>     +------------------------------------------------------------+

     | Ensure that you have read the CircleMUD Mailing List FAQ:  |
     | |

This archive was generated by hypermail 2b30 : 12/08/00 PST