[haiku-commits] Re: haiku: hrev50368 - src/kits/network/libnetapi headers/os/net
- From: Dario Casalinuovo <b.vitruvio@xxxxxxxxx>
- To: haiku-commits@xxxxxxxxxxxxx
- Date: Tue, 21 Jun 2016 17:55:11 +0200
On Tue, Jun 21, 2016 at 5:41 PM, Rene Gollent <anevilyak@xxxxxxxxx> wrote:
On Tue, Jun 21, 2016 at 11:32 AM, Jessica Hamilton
Shouldn't we add padding to these classes like we do elsewhere tominimise
this problem then?
These aren't part of the R5 API, they're new. As such, until an
official release happens, they're subject to change/redesign, so
there's no real point in adding FBC until they're finalized. That's
generally been the policy for new classes across the board, since it
otherwise makes development more complicated than it needs to be if
you're having to maintain compat across random nightlies.
When the release time come and padding is added we will almost certainly
break all apps. I don't see why adding it in the first place would make
development harder. Instead more are the chances we will keep things
working, while at the same time we don't exclude changes breaking the ABI.
It seems easier to leave the padding untouched until R1, and anyway someone
will have to do this work before or after, it's easier to plan it since you
think the class is candidate to be public.
On a secondary note it would be nice if we setup in future ABI breakage
checking across system libs and packages versions along with the buildbots.
Other related posts: