[interfacekit] Re: BString

Mh, let's try again, since the other message got messed up:

> I commented out the class BString from compilation and inclusion in 
> libopenbeos.so, since it is buggy. It does, for instance, crash the 
> BMimeType tests (`tests/UnitTester BMimeType'). Whoever is responsible 
> for it, please be very careful with such a central class, as a lot of 
> code relies on it to work correctly.

Yeah, sorry, my fault.
I prefer to put my code into the CVS even if it's not full tested, since thus 
the code is there, and if my hd crashes I do not lose anything.
If you prefer, I can go the other way round, keep the code locally until I've 
tested it completely.

 
> A good idea is to run the available tests (App/Support/Storage Kit unit 
> tests) with and without the class and compare the logs before 
> committing the change of the Jamfile (or support.src in this case) to 
> CVS. The source can and should of course be tracked with CVS. The only

Yeah, tests. I really need to write unit tests for BString. The problem is that 
I really can't understand why support tests don't compile for me (or is it a 
known problem?). If those tests compiled, I could just add mine and test if 
they work.

> thing to take care about is, that the header file is compilable and 
> binary compatible with the original.

Yeah, this is fine, since I didn't change almost anything in it :)

Sorry again.


-----------------------------------------------------
Invia una cartolina ad un amico!
http://cartoline.supereva.it/index.html

messaggio inviato con Freemail by www.superEva.it
-----------------------------------------------------

Other related posts: