[DGD]compile_object() kfun

[Stephen Schmidt]

On Tue, 13 Mar 2001, Par Winzell wrote:
>  > Design question: Should the update command call create()...?
> 
> Hell, no. That'd kill 98% of the reason for upgrades in the first place;

Yah, that occurred to me about 5 minutes after I sent
the post off. Murphy's Law in action :(

Perhaps as a flag on the update command, update -c or something
like that to invoke create after the update? Or perhaps a
separate command that would call create()?

> typically for a daemon object the create functions reads something like,
 
> 	static void create() {
> 		user_objects = ([ ]);
> 	}
> 
> and when you make a small API modification in your sixth year of running
> a successful commercial game and your 'update' command deliberately zaps
> your user database, as sort of a side-effect of recompiling the code,
> you're going to be pretty damn pissed. :-)
 
But: Surely you would be saving data to a file, and create()
would reload from the file? Or is the persistence so good
that saving to file is no longer needed?

Steve 


"Nearly every historian, including this one, has concluded that to
say of Gideon J. Pillow that he was the President's law partner was
to sum up his military talents."
                                        K. Jack Bauer







List config page:  http://list.imaginary.com/mailman/listinfo/dgd