cppunit requires C++11 capable compiler now
dave at horsfall.org
Tue May 2 22:46:40 UTC 2017
On Tue, 2 May 2017, Michael Dickens wrote:
> The new CppUnit has an interesting issue: #include'ing the header,
> whether directly or indirectly, results in requiring linking to the
> library, because there is a new static variable in the primary namespace
> in the header.
> I think this is poor programming because, as an example, I might
> #include a header that in turn #include's the log4cpp header, but might
> project doesn't use or require log4cpp & this indirect inclusion forces
> it to do so.
That is *terrible* programming practice, and says a lot about the
competence (or rather, the lack) of the programmer(s) involved.
Header files are just that: headers; I don't care what their excuse is.
Dave Horsfall DTM (VK2KFU) "Those who don't understand security will suffer."
More information about the macports-users