La Strega wrote:

I forgot to mark a derivation as virtual.

C++ can be finicky but between it and C they really are the only languages that can fulfill the promise of "code once, run anywhere" despite requiring a recompile to do so.

C++ keeps bizdev contracts out of my hair.

This is almost a dear john letter to C#

Greg Utas wrote:

It's now recommended that only the original function be virtual and that derivations only be override or final. So I guess you're using a version of C++ that doesn't have those tags yet.

class B : virtual public A {}; 

Greg Utas wrote:

That's damning with faint praise given that you have to develop or find portable libraries that start with sockets and go all the way up the food chain.

Greg Utas wrote:

I can see the appeal, but if you have that library that goes all the way down to sockets, you might not escape so easily!

C++

class B : virtual public A {};

Congratulations on what I am assuming was a 2nd prize win for last month.

template<const size_t S> class StaticFileLexContext :public FileLexContext, public StaticLexContext<S> {
    StaticFileLexContext() {

    }
};

Greg Utas wrote:

Without the abstract classes, admixed classes tend to make assumptions about each other, so refactoring is needed to make other combinations work later.

template<const size_t S> class StringBuilder { ... };