Re: [oxid-dev-general] New blog post on planet: Overloading non-overloadable classes - don't!

2015-08-27 Thread Mersiowsky, Daniel
-general-boun...@lists.oxidforge.org [mailto:dev-general-boun...@lists.oxidforge.org] Im Auftrag von Mersiowsky, Daniel Gesendet: Mittwoch, 26. August 2015 15:28 An: dev-general@lists.oxidforge.org Betreff: Re: [oxid-dev-general] New blog post on planet: Overloading non-overloadable classes - don't

Re: [oxid-dev-general] New blog post on planet: Overloading non-overloadable classes - don't!

2015-08-26 Thread Mersiowsky, Daniel
Hi Everyone, I knew this wasn't a good practice, but I wonder how I'm going to adapt module-dependent bootstrap functionality in the future. Example: I'm using a custom Autoloader for registering namespaces at runtime. Every module adds its own namespace by extending oxShopControl::__construct