There are several spots in code that use exceptions:
DataViewerCollection.cppLogManagerImpl.cpp - handling of a scenario when invalid HTTP client module is being passed to it.EventFilterCollection.cpp- HTTP Clients for Android and C API (MIP SDK implementation)
LogManager_jni.cpp - Android only- and a few custom modules - Sid Dahiya (@sid-dahiya)
In general, we do not have that many instances. Core SDK is mostly exception-free.
We need to consider permanently turning exceptions off, esp. for platforms that project the API to other programming languages: Obj-C, Java, Xamarin. In that case we need a mechanism to implement return status codes instead for all places in code, where exceptions may be thrown.
There are several spots in code that use exceptions:
DataViewerCollection.cppLogManagerImpl.cpp- handling of a scenario when invalid HTTP client module is being passed to it.EventFilterCollection.cppLogManager_jni.cpp- Android onlyIn general, we do not have that many instances. Core SDK is mostly exception-free.
We need to consider permanently turning exceptions off, esp. for platforms that project the API to other programming languages: Obj-C, Java, Xamarin. In that case we need a mechanism to implement return status codes instead for all places in code, where exceptions may be thrown.