BDE VS Qt

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/

Qt mono repo : .. you could check out all submodules and simply use CMake to exactly achieve this. A mono repo also means that if I only use qtbase and declarative, I would need to have all submodules in there? - No

For e.g. if you’re writing a framework, you need to interface with Cocoa on MacOS to draw windows, which only provides an Objective C or Swift interface. You can look at the Qt source code and see how they do it: https://github.com/qt/qtbase/tree/067b53864112c084587fa9a507eb4bde3d50a6e1/src/plugins/platforms/cocoa

That's because Qt 6 wholeheartedly converted to CMake for you. (At least it is better than qmake.) In order to support this Qt has this large battery of CMake files [1]. Qt is of course a clear outlier, but you can't expect the same level of support from every other library you want. My points about "anything exotic" still stand.

[1] https://github.com/qt/qtbase/tree/dev/cmake

What are you talking about? Qt has GTK theme support built-in: https://github.com/qt/qtbase/tree/dev/src/plugins/platformthemes/gtk3

This looks like the Qt bug solved by this commit: https://github.com/qt/qtbase/commit/acaabc9108dfe75530960cf8e3ec4f3602cd82e0

Yeah, I'm sure it's completely unheard of. Oh except that it took me all of a couple minutes to find an example of that exact thing in one of the largest, most commonly used C++ frameworks out there.

I don't see any connect in https://github.com/qt/qtbase/blob/dev/src/corelib/tools/qsharedpointer_impl.h, and QPointer isn't a QObject (though I don't know if the latter is actually necessary for signal-slots). One (unreliable) way to test is to see if a QPointer fails to be nulled out when the QObject is blocked by a QSignalBlocker. Alternatively I'd set a data breakpoint on a QPointer and try it out. But I don't have the time right now.