3 ms·
I find it odd you mentioned libraries and C++ in the same paragraph, when C++ can only deliver libraries in source form and can barely do that. For instance, a
by astrange 8y ago
I find it odd you mentioned libraries and C++ in the same paragraph, when C++ can only deliver libraries in source form and can barely do that.
For instance, all C++ classes are fragile, so their callers have to know their exact memory layout.
And your private ivars and methods, which should be secret, all have to be declared in the header…?
- pjmlp 8y agoLack of experience with C++? I have successfully used plenty of binary libraries throughout the years.
- ncmncm 8y agoLibraries in source form are libraries. The most useful and used libraries for C++ are all, or almost all, source, and there's nothing wrong with that A pattern, in the DP sense, is something you use over and over but can't be put in a library. As the language gets better, the patterns become ordinary library components. Then people start to notice patterns in use of the language plus library, and either capture them in another component, extend the language to enable capturing them, or just rewrite again every time. So a catalog of patterns is really a list of language weaknesses. For an unfixably weak language like C, a list of patterns might be actually useful over the long term. But ambitious people will have moved on to a more powerful language, leaving the incurious, who will not be interested.