
|
[openbeosstorage]
||
[Date Prev]
[04-2002 Date Index]
[Date Next]
||
[Thread Prev]
[04-2002 Thread Index]
[Thread Next]
[openbeosstorage] Re: BDirectory <-> BEntry
- From: Ingo Weinhold <bonefish@xxxxxxxxxxxxxxx>
- To: openbeosstorage@xxxxxxxxxxxxx
- Date: Thu, 11 Apr 2002 12:15:33 +0200 (MET DST)
On Wed, 10 Apr 2002, Tyler Dauwalder wrote:
> 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.
Thus as a consequence the StorageKit:: types have to be declared in a
public header. Understanding kernel_interface.* as an internal layer
between the storage kit classes and the kernel, this public header should
not be kernel_interface.h as it contains a bunch of functions that are not
meant to be used by the application developer. This implies, that the type
declarations should be moved out of kernel_interface.h.
However, I think, the usage of some of these types is counterproductive
anyway. E.g. such as Stat, StatMember and perhaps OpenFlags.
The reason for that is, that these aren't opaque in the BeOS API. If you
e.g. have a look at the usages of StorageKit::get/set_stat() you will see
that in each case a `struct stat*' is passed, although the formal
parameter is StorageKit::Stat.
Thus either conversion functions have to be added or the StorageKit:: type
should be removed.
CU, Ingo
|

|