John Reid ha escrito:
Hello Joaquin,
Joaquín Mª López Muñoz wrote:
intermodule_holder performs a way more expensive static initialization process than static_holder (basically, it creates a shared memory area and interprocess mutex for communication between the different modules of the program. It only affects static initialization, though, the rest of operations (flyweight creation and passing around) are exactly the same as with static_holder. Another reason for not including this is that Boost.Interprocess (on which intermodule_holder depends) is not universally supported, so making intermodule_holder the default would complicate things for some compilers. Perhaps this is worth documenting.
I'll add a note on this on the docs.
* What is your evaluation of the documentation? Extremely clearly written and well thought out. I would like to see more explanation of the examples. I like the inclusion of the test code.
Any particular example you wished you had more info about? I can try to improve that if you point me to the improvable parts. All of them really, I was hoping to see some of the more important lines of code briefly explained in the documentation.
OK, I can try to revise this. Joaquín M López Muñoz Telefónica, Investigación y Desarrollo