News for hackers. Stuff that matters.

A comment on The C++ Build Process Explained. Parent comment

Re:The C++ Build Process Explained by flukus on Wednesday November 14, 2018 @05:53PM (#18454979)
If java is any guide developers would go out of their way to add interfaces everywhere anyway, often they're essentially header files for the OO gods.
[ Parent | on HN ]
Re:The C++ Build Process Explained by kjeetgill on Wednesday November 14, 2018 @07:18PM (#18455646)
I haven't done any C++ in a while, can you swap out the implementation backing a header?

I suppose at the linker layer maybe but even that is just once globally for the program. Right? The OOP God's demand polymorphism!

If memory serves me, the C++ version is a class with all empty virtual functions.

[ Parent | on HN ]
Re:The C++ Build Process Explained by flukus on Wednesday November 14, 2018 @07:40PM (#18455785)
Yeah, it can only be swapped out at link time (without crazy magic). That satisfies two very common cases though, when there is only one implementation (and the interface is a sacrifice to the OOP gods) and when the second implementation is for unit testing only.

Those 2 plus other crazy rules (like only one interface defined per file) mean that many projects will end up with just as many interface files as a c++ project would header files.

[ Parent | on HN ]