I've seen this: - Multiple/virtual/high-on-crack inheritance: add each function/class has 7 template specialization parameters and 3 macros which expand to

I've seen this: - Multiple/virtual/high-on-crack inheritance: add each function/class has 7 template specialization parameters and 3 macros which expand to templates which expand to macros - Lookup using dynamic structures from hell – dictionaries of names where the names are concatenated from various pieces at runtime, etc. think maps of maps of maps loaded from configs of configs - Dynamic loading and other grep-defeating techniques obviously everything has to be a "plugin" - A forest of near-identical names along the lines of DriverController, ControllerManager, DriverManager, ManagerController, controlDriver ad infinitum – all calling each other a 1000 times yes! yes!!! DriverController inherits from ControllerManager which extends ManagerController which contains a DriverManager which agregates 3 ControllerManager from diferent namespaces. I've seen a DriverController function going through 12 levels of stack passed between 3 threads to eventually call back a function from the same DriverController - Templates calling overloaded functions with declarations hopefully visible where the template is defined, maybe not if a template technique exists, it had to be used! - Decorators, metaclasses, code generation, etc. etc. Of course they define their own DDL with xmls parsed by a combination of Python and awk which generates C++ macros which are used in templates to dynamically load plugins which hold maps of maps of function pointers to create3 events dispatched on a pool of threads