-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi,
On 07/31/2010 12:57 PM, Andreas Schamberger wrote: > 1) I'm not so happy with keeping the ezc prefix. As far as I recall it > wasn't really considered to change the class prefix to zeta. Ok the > reasoning is valid but wouldn't this big step of moving to Apache justify > the change? If we don't change it now it'll maybe stay forever ... Using > the autoload files for a conversion script would be a save way to do the > conversion. we considered several ways for changing the class prefix. A fundamental requirement here is, that people must be able to migrate smoothly. BC has always been one of the major concerns of eZ Components and we want to keep it that way. Script based migration is not fully possible, due to PHP's dynamic nature. For example, if you're using call_user_func() and friends, conversion is likely to fail. We could therefore not guarantee that migration to a new class prefix works flawlessly. We also discussed several approaches of providing a BC layer for changed class prefixes, but none of them worked out. In the end, we decided to keep the class prefix in a first step: It is not that important to change it, that we might risc annoying users with migration hassle. If you have a fully functional approach to changing the class prefix, feel free to discuss it here. We are surely open for anything. :) Regards, Toby - -- Tobias Schlitt http://schlitt.info GPG Key: 0xC462BC14 Want to hire me? Need quality assurance? http://qafoo.com eZ Components are Zeta Components now! http://bit.ly/9S7zbn -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAkxUCtAACgkQ5bO3TcRivBS73wCgi4RXOxy/diRujA8Y4wVWBuci ptcAn0Mfp6CZGk5Kb4qo3OVYnf1nCHu5 =2YGk -----END PGP SIGNATURE-----
