Nicolas Weeger wrote: >> I don't see any big issues. But I almost wonder if it would just be >> easier to link in the plugin at compile time to fix those problems. > > > You mean, link python plugin instead of loading it at startup? > It'd be less flexible, since you couldn't just drop a .so / .dll in the > plugins path. Or i'm wrong on what you mean? Correct - just link it in instead of dynamic loading it. At current time, there is really no downside. There is only a downside if other plugins are added, and for some reason they can't be linked in at run time. But as I think about it, the plugin code problem looks for what plugins it finds to to know what is available, so that logic all wouldn't work (it'd have to have something to examine what was already linked in for example). So maybe not as easy as I first thought. _______________________________________________ crossfire-devel mailing list crossfire-devel at lists.real-time.com https://mailman.real-time.com/mailman/listinfo/crossfire-devel