Crate message_plugins

Re-exports§

Plugin: In this architectures, plugins are purely slaves: they simply react to messages. Their only way of returning information by default is by returning Some(status) to signal that they wish to be dropped. If you want your plugin to be able to communicate back to your application after some of your messages, you should hand them a channel to do so through your message type.

construct_plugin: A default for construct_plugin_with_constructor, which will call a function named plugin_constructor. The constructor function is the only function where you need to dirty your hands with extern "C". Its sole purpose is to insert your boxed plugin into a pointer. I suggest writing a constructor of the style:
construct_plugin_with_constructor: Loads a dynamic library at path, and calls the function called constructor in order to instanciate a Plugin. The constructor function is the only function where you need to dirty your hands with extern "C". Its sole purpose is to insert your boxed plugin into a pointer. I suggest writing a constructor of the style:
insert_instance: Inserts a plugin into an uninitialized pointer, preventing the drop on the uninitialized memory that would happen with a simple assignment