On Mon, Jul 09, 2007 at 12:44:09PM +0200, Marco wrote: > >What might be nice is a patch to PHP4 that provides a bit in > >error_reporting > >that would cause warnings on stuff that might break on a move to PHP5. > > > >Someone could then switch it on and look at what is logged. I suspect that > >many people would also be pleasantly surprised that 4 -> 5 is not as hard > >as it seems. > > > I think this is a good idea but might be hard to implement.... thinking > about it couldn't we do something along these lines in userspace? IOW create > a script which parses php files and flags up possible issues?
Replying again: the other thing is that this mode does not need to do everything, it needs to focus on the things that are hard to do by other means; eg: 1) warn on assignment of an object -- this is hard do to by 'eye balling' the code. 2) be silent on the use of a user defined function with the name 'clone' The user can find this by the use of grep. A list of things like (2) should be given and it made clear that (1) WILL NOT point them out. -- Alain Williams Linux Consultant - Mail systems, Web sites, Networking, Programmer, IT Lecturer. +44 (0) 787 668 0256 http://www.phcomp.co.uk/ Parliament Hill Computers Ltd. Registration Information: http://www.phcomp.co.uk/contact.php #include <std_disclaimer.h> -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
