
|
[openbeosstorage]
||
[Date Prev]
[04-2002 Date Index]
[Date Next]
||
[Thread Prev]
[04-2002 Thread Index]
[Thread Next]
[openbeosstorage] Re: BNode:set_fd and other things
- From: Tyler Dauwalder <tyler@xxxxxxxxxxxxx>
- To: openbeosstorage@xxxxxxxxxxxxx
- Date: Sun, 14 Apr 2002 00:56:23 -0700
> > > I wonder, if BDirectory::fDir/fDirFd will be needed at all. At least
> > > until
> > > now I see no reason, why the file descriptor used by BDirectory should
> > > be
> > > a different one than that of BNode. Perhaps I'm missing something, but
> > > I will see as soon as the test suite is done and the class is
> > > implemented.
> > > However, friend classes will use get_fd() anyway.
> > Yes, I know what you mean. I haven't done any tests to figure out
> > whether or not it's necessary.
> That leads to the general question of integration tests. Some tests of
> this kind are already included in the unit tests, but e.g. in the case of
> BFile or BDirectory I don't test any inherited functionality. Perhaps some
> of the base class (BNode, BEntryList,...) tests can be made reusable for
> derived classes? E.g. providing a function that takes a pointer to a base
> class instance and performs tests on it.
That probably would be a good idea. It'll most likely require some serious
restructuring in NodeTest.*; I'll add it to my todo list. :-)
[...]
-Tyler
|

|