How about using the magic identifier "_module_value" which is already allocated for such purposes? If it exists as a constant, use that value as the module value instead of cloning the program.
/ Marcus Comstedt (ACROSS) (Hail Ilpalazzo!)
Previous text:
2004-03-31 18:28: Subject: Re: ADD_FUNCTION() macro on pike 7.5 ?
I don't see why you would need any changes.
to replace ADD_FUNCTION() to add_function_constant() to workaround this change.
That seems like a very strange work around to me. The obvious one is to instead do a wrapper like the one that pike -x module would.
NB: I also think those wrappers are messy and should disappear again. I think it's better to let C modules be objects (in the static case too) and perhaps have a magic constant to let them tell that they don't want to be cloned.
/ Martin Stjernholm, Roxen IS