[openbeos] Re: BObjectList vs. TypedList

> Ingo Weinhold <bonefish@xxxxxxxxxxxxxxx> wrote:
> > > We might also just move it into os/support/, shouldn't we?
> > If we intend to declare it a public API, we should do that. Then we 
> > should
> > make sure, that the usual binary compatibility precautions are 
> > taken
> > (for _PointerList_).
> 
> Perhaps we should have a closer look at the class interface anyway - 
> Be 
> itself introduced a whole new set of such classes with Dano (but not 
> BObjectList), perhaps we might prefer to go a similar way, too.

I'm all for it, though we should probably rather wait till R2. Better 
not add too much potential for problems with the release that is 
basically intended to clone BeOS R5.

> >[...]
> > > Of course, someone should then work on a DiskProbe replacement 
> > > sooner
> > > or later :-))
> > DriveSetup? Well, at least an almost empty implementation already 
> > exists
> > in the tree. BTW, since DriveSetup uses the DriveSetup add-ons 
> > directly
> > (not through the Device API), and we are not going to replicate 
> > this
> > interface, this has to be done anyway.
> 
> No, not DriveSetup, *DiskProbe* - the hex editor that come with BeOS. 
> The Device API is widely used in the applications shipped by Be.

You're sure, that it does? At least mine doesn't seem to (`strings 
Device' produces nothing suspicious). Besides the three ones mentioned 
earlier, Installer, CDBurner, bootman, clockconfig (for whatever 
reason) and writembr show signs of usage of the API.

CU, Ingo

Other related posts: