Introduce a proper plugin system#97
Merged
Merged
Conversation
Co-authored-by: Copilot <copilot@github.com>
efe1211 to
4905060
Compare
Co-authored-by: Copilot <copilot@github.com>
…ires into Malcohol/pluginInterface
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
A proper interface for dynamically loading plugins.
Plugins are not expected to work across versions or different build environments, since deep C++ dependencies are expected to exist between plugin and host. However, some flexibility can exist and I've tried to make the plugin handshake somewhat robust, at least to the extent of issuing informative errors when possible.
In this initial commit of plugin functionality, all plugins are automatically loaded during start up.
Changes: