Elysian Shadows

lol, shit.

Success! That is supremely satisfying. Thaaaaanks!

omg I hope you're right, Falco. That would be the coolest thing ever. It's pretty amazing that you can guess that.

I'm trying it right now and I'll let you know if it works.

Thanks so much!

short wrote:If it's really doing this, then I'm not sure. Perhaps someone else on the forum, or stack overflow

Yep, it is really doing that. Thanks very much for your responses though I really appreciate it. I hope I can find an answer. This is killing me!

instance is of type SingletonInterface, not SingletonImplementation. It's true type is SingletonImplementation, but it is being stored as SingletonInterface. Your SingletonImplementation function "definition" isn't being optimized out, it's being ignored because instance is being stored a...

Haha jk, but inside SingletonInterface.h you should be declaring interfaces (function definitions) not bodies. First of all, "declaring a function interface" and a "function definition" are not the same thing :) { return true; } is the definition. I think that's what you meant b...

When I compile the following code, the functions implemented by SingletonImplementation seem to be optimized out of the build because they are never being called. Even though my SingletonImplementation::createInstance() is creating a new SingletonImplementation, the functions of its parent class are...