At 07:18 PM 12/2/2003 +0100, Christian Schneider wrote:
Marcus Boerger wrote:I see all your concerns. But from my point of view pear has (of course) the problem that it is written in php4 and for php4. So PEAR needs to address the move towards php5 code anyway. An optional E_STRICT would help here wouldn't it?
[My concern is that if E_STRICT warns about var then PEAR developers are tempted to change their code to PPP. This will screw PEAR users who are (for whatever reason) stuck with PHP4.]
Ok, let's take a step back and ask why you want people to change var to public in the first place: I assume you want to make people rethink how they use member variables and promote safer programming. Am I right so far? Now I have the feeling that if you deprecate var you simply make people search and replace var by public globally. Nothing gained at all. What you really want is that people can change var to PPP one by one after carefully examining the usage of a variable. Having grep var * as a tool to identify places to be examined is great, if I replaced all var by public in the first place I lose this. And no, I don't believe in forcing people to stop developing for a week and go over all their code at once to migrate it to the new model. Maybe you see an analogy with my __clone() reasoning here (-:C
- Chris
-- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
