Can using formatting pointers change your OO design methodology?

Question

After switching from C ++ to C ++ w / boost, do you think your OOD skills have improved?

Did you notice patterns in the “normal” C ++ code that you don’t think are included, or do you find that it allows you to create a more abstract design?

I think I'm really interested in whether you use it as a tool or change your approach to OO design in order to use objects more efficiently when using force pointers.

Edit: Summary

This question was strange - I asked because I came across so much C ++ code that was not OO at all. I am sure (with this, and my work on it, before moving on to a managed language) that it is more difficult to think in OO in C ++ than a managed language.

From a look at these posts, I assume that you will find out the value of OO before finding the need for a better way to manage memory, so by the time you start looking for something like Boost, you are already using OO methodologies quite heavily.

I kind of expected a bunch of answers saying that it helped them think in OO, but now that I think about it, if you are not using OO, formatting pointers are not very useful and you won’t see the need for them (so you would not answer).

Answer 1

++, , , . , . (, boost...)

, , . - . , , , . , , . , , , .

, : . , , , . , , . C ++, ( C ++, ?) , . , !

Answer 2

STL/Boost - . . : Boost OOD.

Answer 3

, . Boost.Graph Boost.PropertyMap , , "" , () , , ( ) , - . .

, , Boost . Boost - , !

Answer 4

boost::bind ( boost::function), , ( "" java/# -speak). .

, , IActionable*, , , IActionable . Post-boost , boost::function<void()> -, , boost::bind.

: , , , , , , "" "" .

, , , .

Answer 5

For me, this has not changed the way I design, but Boost gives me additional tools, so some things are simpler. For example, with smart pointers, I no longer need to think about certain object creations being destroyed at the right time (mostly in an exceptional case). But, like any tool, I have to understand when to use them, and NOT.