cpp file that include a header file that publishes such a dependency.
Imagine writing a larger project with many many. Compiling this with "g++ -c" takes about 1 sec on my laptop.Īdd a tiny amount of code that "parses" the string literal "3" (which I think is not valid JSON actually. Just write a short test.cpp with #include in it and add a int main(). When you run "g++ -E" on it (to do the preprocessing step only) those 24000 lines will unfold to about 84000 lines. The project consists of many many files, but most notably it is a C++ header-only library consisting of 24000 lines of header files to be included into every (transitively) dependent. Last I checked, a git clone of this library downloaded 260 Megabytes of data. Should be doable in an afternoon.īut if you disagree, you should try a particular, very popular JSON library for C++ (removed the mention of the name here, you can figure it out on your own if you want). cpp file should be plenty to write a solid reusable implementation that parses to a generic tree (dicts, lists, float/string/bool literals). I would say 50 lines of header + 500 lines of. I think writing a JSON parser should be perfectly fine, it's quite a simple format (while imperfect and probably way overused). But if you can just do that anyways, the actual tests are less important. I've heard it described before that half of the benefit of unit testing in these languages is forcing yourself to structure code in testable modules with clean interfaces. Unit tests are a lot less important if you have a good type system and compiler checking things already. IMO, they're much more suited to building apps in dynamic languages. But if you don't care to do that, nothing's as fast and clean both to develop and for the end-user to use as every platform's native framework. Yup, it'll be a major pain to ever port to another platform. Writing GUI apps against the native framework. Maybe then it's okay to trade off raw speed for not handing a ton of formatting and syntax edge cases. I guess it's sort of okay if you expect to only be reading your local config files versus arbitrary web content. Rolling your own JSON, XML, etc parsers raises some eyebrows. Upvoted for a number of interesting and unconventional opinions.
0 kommentar(er)
