16 Sep
2024
16 Sep
'24
4:25 p.m.
чт, 12 сент. 2024 г. в 17:29, Julien Blanc via Boost
i think the following can be done quite easily:
* the macro to opt out from gdb pretty printing already exists, move its usage from inside gdb_printers.hpp to config.hpp * provide a public (ie, not in details) json/debug_printers.hpp file, which unconditionally includes gdb_printers.hpp, to opt-in again. This file shall not be included by any library code.
This allows client code to circumvent the limitations, and is fully transparent for users not affected by the duplicated python code issue.
I can file a PR if you are ok with this approach.
Sure, sounds like a good idea.