On 01/04/2013 06:00 PM, tamouse mailing lists wrote:
On Fri, Jan 4, 2013 at 6:09 PM, Matt Pelmear <mjpelmear@xxxxxxxxx> wrote:
On 01/04/2013 01:40 PM, tamouse mailing lists wrote:
One should be able to solve parsing problems without resorting to using a
web server. Every time I save a php file, I have my editor set to run it
through php -l. Saves lots of angst when I get to the web testing stage.
This is a good idea in general. It's also a good trick to check for this
problem from the command line when suspecting a parse problem. Most IDEs
will make parse errors very obvious while you are editing the file, too.
Unfortunately not all members of any given development team can be relied
upon to test things in this way before committing ;)
Committing a syntax error which breaks integration is a HUGE HUGE NO
NO. Such a person would likely be cast from a dev team, or relegated
to some more benign task.
Yup. Again though, not everyone is so lucky as to only work with true
professionals at all times. I've personally managed dev teams that are
anywhere from largely green developers to largely seasoned
professionals. Sometimes you have to work with what you have.
But we digress...
--
PHP Database Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php
