Hi, > Please don't construe the willingness to add E_STRICTs with agreement > that such code should be forcibly eliminated. If there were a fully > automated tool to bring code into compliance, I would feel a lot better > about such changes, but even then, many of us would be applying that > tool to third-party code that has been lying around for a decade > untouched, and that's scary.
such a tool has been proposed and even without it, it's a matter of (tedious) search & replace; > I suppose my opinion on these things is formed by my life experience > with these issues and since I don't doubt we all mean well, I guess the > OO purists probably are approaching this from different life > experiences. Here is where I'm coming from: This is not about purism. Leaving support for PHP4 constructors in the code means this code must be maintained for every core change that affects constructors. > To this day, we > still don't use namespaces or exceptions. No part of PHP forces you to write your code this way. You can still work with "Error classes" or "Error return values" and so on. -- Ralf Lang Linux Consultant / Developer Tel.: +49-170-6381563 Mail: l...@b1-systems.de B1 Systems GmbH Osterfeldstraße 7 / 85088 Vohburg / http://www.b1-systems.de GF: Ralph Dehner / Unternehmenssitz: Vohburg / AG: Ingolstadt,HRB 3537
signature.asc
Description: OpenPGP digital signature
