Updates to transition manual needed

[dpward]

The transition manual does not cover some of the breaking ABI changes that have occurred in libyang 5.x after 5.0, such as removing the LYD_ANYDATA_VALUE union (2f58b41), or removing the lyd_new_term_bin() function to add a new terminal node with LYB formatted data (ae63fde). Can this please be updated?

[choppsv1]

Perhaps more importantly why were the _bin functions removed? We were definitely under the impression that if we stuck to binary as much as possible, rather than constantly parsing strings, that we should expect better performance.

So does this mean that we are stuck parsing string data at every turn now?

FWIW, the API size args that changed meaning from bytes to bits, then the API functions removed, binary formats left but returned (thanks); I wish the benefits were more obvious for having to adjust to all this API churn -- other than we must adapt if we want to get bug-fixes.

[choppsv1]

[@michalvasko]

I mean, we're now going to have to allocate a stack buffer and sprintf() uint64_ts into it so that we can then pass that string to lyd_new_term(). Is this better? What is libyang going to do with this string? What if we are using binary encoding to pass data around?

I saw a comment regarding this change that said something like "binary encoding is complex", but wouldn't it still be more efficient to load the initial value directly into a uint64_t to manipulate further, rather than first printing it to a string and then parsing that string only to put it into some more compressed binary format?