I'm now aware that JAPI intends to support more than just C++ with its library API, hence why it's limited to having a C-interface.
However, since JAPI itself is programmed in C++ and a lot of the plugins are also programmed in C++, what about having the option of using a dedicated C++ API? Obviously this would take more effort to implement than just having one thing to cover all bases, but I feel it'd be worth it for the convenience.
Some benefits I can think of off the top of my head:
namespace japi or namespace JAPI for functions like japi::LogInfo() and even variables like japi::AsbrBase
- Use of C++ types, like
std::filesystem::path and std::string
- Potentially easier hooking
I'm now aware that JAPI intends to support more than just C++ with its library API, hence why it's limited to having a C-interface.
However, since JAPI itself is programmed in C++ and a lot of the plugins are also programmed in C++, what about having the option of using a dedicated C++ API? Obviously this would take more effort to implement than just having one thing to cover all bases, but I feel it'd be worth it for the convenience.
Some benefits I can think of off the top of my head:
namespace japiornamespace JAPIfor functions likejapi::LogInfo()and even variables likejapi::AsbrBasestd::filesystem::pathandstd::string