Mind you, I think C++ as a whole went over the line long ago and became a kind of reducto ad absurdum on OOP. Much better to choose the relative sanity of Objective C or Python. But it's not like you have any choice about it at this point, tho. You're in bed with him, better hope his not the Devil.
I could be convinced that templates in general were a bad idea for C++, but if they're going to exist at all, they should work in all their permutations. Including allowing pure virtual functions in template classes. It might be pretty difficult to come up with an example where using them is actually the best solution, but when that situation comes along, I don't want to discover that the compiler doesn't support it, and I *certainly* don't want to discover that the compiler doesn't support it because the compiler writer decided it was "evil".
![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png){kind=small}
no subject
no subject
(Draw your own conclusion.)
You gotta be kidding...
Mind you, I think C++ as a whole went over the line long ago and became a kind of reducto ad absurdum on OOP. Much better to choose the relative sanity of Objective C or Python. But it's not like you have any choice about it at this point, tho. You're in bed with him, better hope his not the Devil.
no subject