walter-erquinigo wrote: > That expectations, combined with the fact that LLDB has plugins, makes it > really sound like lldb_plugin is the interface we expose for writing > (dynamically loadable) plugins.
I don't think people would have the expectation that you need to use `lldb_plugin` for a namespace of a dynamically loaded plugin. In fact, an external shared library is free to use any namespace because you only need to provide the symbol PluginInitialize to make LLDB happy. An in any case, if you used `lldb_plugin` for your plugin, there would be nothing wrong, tbh. If we go the lldb_plugin route, we could try to standardize: lldb_private -> core lldb symbols that don't belong to a plugin lldb_plugin -> symbols from any plugins lldb -> public ABI-stable symbols https://github.com/llvm/llvm-project/pull/68150 _______________________________________________ lldb-commits mailing list lldb-commits@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
