[openbeosstorage] Re: latest update

On Sun, 28 Apr 2002, Tyler Dauwalder wrote:

> > I commited the BEntry related changes. While doing so, I saw, that I
> > forgot to implement entry_ref::operator<(). BTW, I don't really know, what
> > it is good for. I hope it has the obvious semantics.
> 
> Maybe it's something like "/" < "/boot" < "/boot/develop". Where is that 
> declared? It's not in the R5 Entry.h is it?

I didn't look it up in the R5 header (and don't have a BeOS machine at
hand at the moment), but it was commented in our header, so I guess, it
is in the R5 header too. However, whereever it resides, it is at least 
there, since the extended BEntry tests use it (and do compile). :-)

BTW, it compares componentwise in order device, directory, name. Since it
is declared a non-member, it is certainly used for things like sorting
algorithms...

> So where do we stand now? Is BNodeInfo the only pre-alpha class that's not 
> finished yet? Other than BEntry doxygen, which I might have time to work on 
> a bit tomorrow (no Chem lab this week :-))).

It's certainly a question of definition, but after having a look at
BNodeInfo, I don't think, it should be a pre-alpha class, as it shouldn't
need any kernel interface support. As I understand it, it uses BNode's
attribute functionality and some (AFAIK) BMimeType stuff to provide some
more sophisticated information about a node.

OTHO, I think BVolume should be marked pre-alpha. I haven't had a look at
it in the BeBook though, so I maybe shouldn't argue about it. But as far
as my imagination carries me, it is a dev_t wrapper classes. Pretty  
basic. We need it for BStatable, find_directory() and probably some
classes I currently don't think of.
BTW, Vincent, what about a basic non-implementation?

Oh, I forgot to mention, the other day, when I took a look in the BeBook,
I encountered BAppInfo. It's not listed anywhere, is it?

CU, Ingo

Other related posts: