FreeLists / openbeosstorage / [openbeosstorage] Re: BVolume, BVolumeRoster, friend vs. protect

[Tyler Dauwalder <tyler@xxxxxxxxxxxxx>]

> Tyler, if it's all right with you, I'd like to get started on implementing
> BVolume and BVolumeRoster.

Sounds like a plan to me. Go for it.

> I think it makes sense (no pun intended) to mark all the data members of 
> the base classes we are re-implementing as private, with public (non-virtual) 
> accessors that may be called from other classes or sub-classes. 

I'm not sure we're both thinking of the same thing. Here's 
what I am proposing in different words:

+ The public interfaces will remain identical to those from R5 (i.e.
no new public members will be added).

+ No protected members will be added.

+ All data members will remain private. We'll use friends for classes 
that need access to the private data members of other classes, but we'll
restrict ourselves to private accessor functions only (i.e. no direct
manipulation of the private data members of other classes).

> I've read the other threads and also think code reviews are an excellent 
> idea. A round-robin type of code review sounds good to me, since that would 
> expose all of us to each others' work and give us a more concrete idea of our 
> progress, as well as contine to spark inspiration (:o).

Fair enough :-). As far as I'm concerned, anyone interested in helping
out when the time comes is welcome to.

-Tyler