[openbeos] Re: binary middle ground

> The thing that disturbs me somewhat is that other (Be published) apps might
> use unpublished APIs. :-/ That could force us to bundle certain kits together.
> The issue with BONE and the printing kit is a good example.

I'm unaware of the BONE/printing kit problem, but you have a good
point.  Fortunately, none of the Be published apps are on the scale of,
say, Word for Windows. =)

> >- Class names and inheritance hierarchies must be the same
> >- Public and protected function signatures must be the same
> >- The vtable layout must be the same
> >- The data size of classes must be the same
> 
> Public data has to be exactly the same. Private data, though, doesn't.

True, though there is thankfully little public data in the BeAPI (aside
from structs, of course).

e

Other related posts: