Re: Programs not running
| From: | Karl DeSaulniers | Date: | Sat, 05 Jan 2013 06:48:56 +0000 |
| Subject: | Re: Programs not running | ||
| References: | 1 2 3 4 5 6 7 | Groups: | php.db |
| Request: | Send a blank email to php-db+get-48614@lists.php.net to get a copy of this message | ||
On Jan 4, 2013, at 8:00 PM, tamouse mailing lists wrote:
On Fri, Jan 4, 2013 at 6:09 PM, Matt Pelmear <mjpelmear@gmail.com> wrote:For those of us who have no idea of what you speak, can you elaborate so as we don't make that mistake? Or are you just talking about submitting a file to production without testing it? I personally have not used command line. It is new to me, but sounds integral. Where can one study its use? Best, Karl DeSaulniers Design Drumm http://designdrumm.comOn 01/04/2013 01:40 PM, tamouse mailing lists wrote: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. --PHP Database Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.phpOne 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 ;)