On 03.05.2017 07:43, Honnappa Nagarahalli wrote:
> Let us say:
>
> API spec v1.20 could define:
>
> typedef struct odp_foo_bar_t {
> /** This is foo*/
> uint8_t foo;
> } odp_foo_bar_t;
>
>
> API spec v1.30 could define:
>
> typedef struct odp_foo_bar_t {
> /** @deprecated Foo is deprecated, use bar instead. */
> uint8_t foo;
>
> /** This is bar */
> uint8_t bar;
> } odp_foo_bar_t;
>
> Application (with out any changes) moves to v1.30, it still compiles and runs.
>
> Application writer checks what is deprecated by searching for
> '@deprecated' or looking at the release notes and changes his code for
> v1.30.
This does not work. Nobody reads release notes in check for deprecated
API until his piece of software breaks horribly. Even we do not do that,
as demonstrated by Petri's patch 3/4.
--
With best wishes
Dmitry
