> Well, being listed in a public header doesn't mean, that they are
> public. They appear as friends of BRegion, because they certainly
> access BRegion internals, but since they are completely undocumented
> (unless I miss something), I would consider them private. If an
> application developer uses them, they risk their app to break with a
> later release.
Makes sense :P
>
> > Moreover, the BRegion public methods just call those C functions
> > (some stack crawl confirmed this).
> > For example:
> >
> > BRegion::Include(clipping_rect rect)
> > {
> > BRegion region;
> > BRegion newRegion;
> >
> > region.Set(rect);
> >
> > and_region(this, ®ion, &newRegion);
>
> Mmh, I would expect something like an OR here :-P
Heh, right :=) But dont' worry, it is correct in the implementation... this
wasn't a cut&paste :=)