Libnop: C++ Native Object Protocols

Re:Libnop: C++ Native Object Protocols by sytelus on Saturday October 06, 2018 @02:29AM (#18153841)

Code generators and schema files are not a good feature, IMO. One shouldn't have to duplicate everything in yet another "neutral" language and then maintain two copies of definitions.

The header-only libraries are good. Less dependency is good. No need for build system is good. Many of the existing solutions you mentioned have tons of dependencies. When code needs to be built reliably on 3 different OS and interfaced with arcane twisted build systems, dependencies become nightmare. Boost is great overall but I rather avoid this monster if I can.

[ Parent | on HN ]

Re:Libnop: C++ Native Object Protocols by CamouflagedKiwi on Saturday October 06, 2018 @02:43AM (#18153890)

You're using them wrong if you duplicate everything and maintain two copies. You should have one copy of the objects in the "neutral" language (protobuf or whatever) and compile the language-specific files out of that - but you don't maintain those any more than you maintain any other build output.

[ Parent | on HN ]

Re:Libnop: C++ Native Object Protocols by je42 on Saturday October 06, 2018 @06:26AM (#18154425)

Code generators are good - if they are properly supported and tooling good. Have a look at the new work-in-progress about C++ meta classes (P0707): https://youtu.be/80BZxujhY38?t=3141 this stuff looks very neat.

[ Parent | on HN ]