Comment 3 for bug 1302656

I've created a branch that mangles the major version number into the scope's create function symbol, so we can detect if a scope is ABI incompatible by looking through the symbol table (instead of having to call ScopeBase::start()). This change is ABI incompatible (but source code compatible), so scope source code doesn't need to be changed.

lp:~michihenning/unity-scopes-api/add-version-to-create-function-name

For now, only the major version number is checked, until we get around to dealing with bug #1320026.

We still have the int that is returned from ScopeBase::start(). With the version mangled into the create function name, forcing the scope author to return the version from start() is redundant really. It seems it would be cleaner to change start() to have void return type.

Opinions anyone? I'm thinking that we could lump this in with Pawel's recent incompatible changes.

Please speak up, I don't want to merge-propose this half-baked.