Re: Command line PHP
| From: | Robert Cummings | Date: | Fri, 07 Jan 2011 18:46:37 +0000 |
| Subject: | Re: Command line PHP | ||
| References: | 1 2 3 4 5 6 | Groups: | php.general |
| Request: | Send a blank email to php-general+get-310566@lists.php.net to get a copy of this message | ||
On 11-01-07 01:31 PM, Joshua Kehn wrote:
On Jan 7, 2011, at 12:34 PM, Daniel Brown wrote:I disagree... many of my cron/shell scripts leverage the very codebase that the site works on to do things for the site from the command-line. Why would I use another language that would require re-implementation of existing functionality? The right tool for the job depends on the job in question regardless of someone else's perception of the intended purpose of the tool. Cheers, Rob. -- E-Mail Disclaimer: Information contained in this message and any attached documents is considered confidential and legally protected. This message is intended solely for the addressee(s). Disclosure, copying, and distribution are prohibited unless authorized.On Fri, Jan 7, 2011 at 12:18, Joshua Kehn<josh.kehn@gmail.com> wrote:My apologies. I just view PHP as a perfected web language, due to it's templating nature, while using it for other things (scripts, utilities, cron) is a misuse in my opinion. It does completely depend on your mastery of the language. If you're very good with PHP and you don't often do non-web things it might not make sense to learn another language as well.Using another language more suited towards CLI / standalone (non-web) development would be easier. PHP at it's core is a templating language. I don't think it is as suited as say Python for developing standalone applications.One might argue that it depends on your mastery of and comfortwith the language. That in mind, the same is true of nearly any programming language.And thanks for reminding me of what PHP is at its core. ;-P-- </Daniel P. Brown> Network Infrastructure Manager Documentation, Webmaster Teams http://www.php.net/