Deprecations can easily go unnoticed because they are only mentioned in sentry.h doc comments.
|
/** |
|
* Sentry SDK name set during build time. |
|
* Deprecated: Please use sentry_options_get_sdk_name instead. |
|
*/ |
|
SENTRY_EXPERIMENTAL_API const char *sentry_sdk_name(void); |
Is it possible to make deprecations more visible with a deprecation macro that expands to __attribute__((deprecated)) or __declspec(deprecated) for compilers that are known to support them? With this, at least most GCC/Clang/MSVC users could get feedback when using deprecated APIs.
Deprecations can easily go unnoticed because they are only mentioned in
sentry.hdoc comments.sentry-native/include/sentry.h
Lines 2574 to 2578 in 0922029
Is it possible to make deprecations more visible with a deprecation macro that expands to
__attribute__((deprecated))or__declspec(deprecated)for compilers that are known to support them? With this, at least most GCC/Clang/MSVC users could get feedback when using deprecated APIs.