BDE VS Yomm2

Hi, one of the authors here. BlazingMQ depends on two other open source C++ libraries: https://github.com/bloomberg/bde and https://github.com/bloomberg/ntf-core. I believe documentation writer wanted to highlight that BlazingMQ does not depend on frameworks like ZooKeeper, etc.

It would be easy to make the runtime use polymorphic allocators, one for the temporary objects created by update_methods, and another for the hash and dispatch tables. The first allocator could use the stack (like this), and the second a block in the BSS segment.

I'm pretty sure they use C++ very extensively. They have their own C++ standard library for example. I'm not aware of them using FORTRAN or C. Do you have a reference for that?

No first-hand experience, but C++ is definitely a player. Check out John Lakos and bloomberg/bde. He was a force behind the improved allocators in C++11 and beyond. That repo I linked is a beast of a codebase (:

Specifying your own allocator is like a main feature of bde from Bloomberg:

https://github.com/bloomberg/bde

If I remember correctly, BDE ( https://github.com/bloomberg/bde ) is developed in London's office and definitely the team that works on it is one of the most experienced in the company.

Libc++ hasn't implemented polymorphic containers and similar. You could take a look at what inspired PMR: https://github.com/bloomberg/bde/

More information about virtual_ptr is available in the documentation.

YOMM2 is available on GitHub.

And if you don't want to put a virtual function or have a base class, etc. check YOMM, which was recently mentioned in r/cpp.

I have a visitor themed example. I will update it to implement the visitor solution as well, for easier comparison.

the main README

I am publishing and documenting some of the internals of my YOMM2 library. I adopted the same style as cppreference.com. My library uses two constructs nested inside a class. cppreference documents template like this and their members like this. However, I use two constructs that are, AFAICT, not used in the standard library, so there is nothing for me to ape.

I don't know much of type theory, i'm just saying that i don't see when this could be useful in real life. On the other hand, multimethods such as what the Julia language has or, in C++, yomm2, sounds much more useful, as you can have two object *a, *b and calling f(a, b) will dispatch on the concrete type of all virtual arguments.