Test the application Diary of boost on VxWorks

Many people think that the boost library is very large and not suitable for embedded development. Therefore, when it comes to embedded systems, boost doesn't even want to pass directly, and it is mostly experienced.ProgramPersonnel, but I think there are too many boxes in our Chinese minds. There is nothing to do, and there is no specific standard for evaluating the quality. The boost library has been developing for a long time, stable, practical, and easy to use, why can't I try it? If I think boost is huge, then STL is not small. Why c ++? Since the C ++ cost is actually included, it is worth a lot of consideration. It is undeniable that many new languages and templates used by boost may not be supported by all compilers, this leaves a hidden danger for transplantation, but it is very useful to the share_ptr tool. It will also be added in C ++ 0x, and there is no harm in using it.

First, you need to test it and then use it on a large scale. The initial steps are as follows:

1. Smart_ptr

2. Xpressive

3. Property_tree

4. Test on the PC to see if it is better than cppunit

 

In these databases, property_tree is estimated to be awkward, and there are many other tools that can be replaced. It doesn't matter. smart_ptr may be widely used. Please try it more.

Xpressive is an advanced product that can be used.

Today, smart_ptr has been compiled on vxworks6.4 and 6.8, but xpressive has been unable to compile it, and an error is reported, which cannot be seen. Later, I took a closer look and found that a definition in boost conflicted with that in vector. I changed the name and found that the error reported by workbench was not a Red Cross, it must be noted that the error is correct...

You will have the opportunity to try it on the board tomorrow.