Go to the FreeLists Home Page Home Signup Help Login
 



[openbeosstorage] || [Date Prev] [04-2002 Date Index] [Date Next] || [Thread Prev] [04-2002 Thread Index] [Thread Next]

[openbeosstorage] Re: BDirectory <-> BEntry

  • From: Tyler Dauwalder <tyler@xxxxxxxxxxxxx>
  • To: openbeosstorage@xxxxxxxxxxxxx
  • Date: Wed, 10 Apr 2002 10:36:11 -0700
> What leaves a bit of a bitter taste when using StorageKit:: types in a 
> public header file is, on one hand that you then have to make
> kernel_interface.h a public header, too, 

The reason the StorageKit:: namespace exists, though, is to delineate the parts 
of the kit that are to be considered private (being open source, we can only 
hide things so much :-). The doxygen description of StorageKit:: says something 
to that effect, I believe. So the only place any StorageKit:: members should 
show up in our public headers are in the private sections of our classes.

Now that we may be making some of our interfaces protected, they'll have to 
show up there as well (which is one of the better arguments against going the 
protected route vs. the private/friend route). 

> and on the other hand when
> changing the typedef for one of those type you have to be careful with
> respect to its sizeof(), because you might change the size of a B* class
> instance as an effect.

This is very true. :-)

-Tyler






[ Home | Signup | Help | Login | Archives | Lists ]

All trademarks and copyrights within the FreeLists archives are owned by their respective owners.
Everything else ©2007 Avenir Technologies, LLC.