[interfacekit] Re: Broken BMessage

Erik Jaesler <erik@xxxxxxxxxxxxxx> wrote:
> It is less than intuitive, no doubt there, although I was pleasantly 
> surprized last night to find that even after all this time (I'd guess 
> it's been about a year), the code still makes sense to me.  I will 
> try 
> to fix it as-is so as to get you up and running ASAP.

Great!

> I've also started sketching out a C API for managing BMessage's data 
> as 
> an always-flattened buffer, a la Dano.  I've contemplating this 
> approach 
> for some time, mainly with the idea in mind of having it available 
> for 
> use in the kernel.  At this point, though it would be less 133t (as 
> the 
> young kids like to say ;) than the existing template-based code, it 
> would probably be easier to understand and maintain.  If only because 
> the debugger would be happier.

Although I would like that "always-flattened" method, C++ does work in 
the kernel as well, that alone would not be a pressing reason to switch 
to C.
Of course, it would be available to fewer components there, but not 
many components would make use of it anyway.

Anyway: we'll probably try to not have the kernel understand or send 
BMessages at all (if feasible).

Bye,
   Axel.

Other related posts: