[interfacekit] Re: Broken BMessage

Ingo,

is it possible that the current BMessage implementation is quite broken, or do I miss some important prerequisite?

It is quite possible, yes. Although the various Add/Find/Get functions are fairly well covered by unit tests, several APIs are not and sending is not.

I'm in the process of cleaning up the Storage Kit code to run nicely on our kernel and am experiencing the annoying situation that none of the Storage Kit unit test that require communication with the registrar runs through; all crash in some BMessage code (mostly in some evil template code called by FindData(), but also in Unflatten()).

I have tested Flatten() and Unflatten() to some extent, although there are not any unit tests for it. Would you mind posting your code or pointing out where it is in CVS? I've been pretty well buried by real life for quite some time, but I will make an earnest attempt to track down the problem this week so that you're not held up any longer than possible.

BTW, my template code is not *evil*, merely Very Obnoxious -- it's a matter of intent. ;) In retrospect, the BMessage internals were not the best place to go hog wild experimenting after I finished reading "Modern C++ Design". =P I have recognized for a long time that a rewrite is in order. =\

I was hoping to maybe even get the registrar running on our kernel, but without working messaging that looks rather hopeless. :-(

I apologize for leaving BMessage lying there half-baked. I very much wish my time situation was more allowing of Haiku work. =(

e


Other related posts: