On Tue, Nov 20, 2001 at 11:05:58PM +0100, Thomas Eibner wrote: > Why do you want to use php for the command line? One reason. I don't want to have to rewrite libraries that I've created. If I can't reuse something I've written with any front-end, then what use is it to me? Maybe PHP isn't right for me, period. You don't need to stand on your high-horse and sing to the choir. I was simply trying to give the whole PHP-fanatics a chance to show their knowledge in deploying their language of choice in many different environments. There's always C/C++, Python, Perl, and Java to implement libraries while still allowing for a flexible interface. Yes, PHP is designed for HTML preprocessing and templating, not unlike JSP. Perhaps, I should only think of PHP in terms of a front-end, not a back-end. Perhaps creating a application.so (ala C) to load into PHP would be far better than using PHP "include" statements. Then again... there's the binding of GTK libs to PHP. True, once again a front-end. The same is true of Python, and yes, even Perl or Java. So, why the bias against PHP. Is it simply because the notation reminds you too much of ASP? Is it because the default output for PHP is to wrap things in HTML 1.0 headers and footers? What is it exactly? -- Chad Walstrom <chewie at wookimus.net> | a.k.a. ^chewie http://www.wookimus.net/ | s.k.a. gunnarr Key fingerprint = B4AB D627 9CBD 687E 7A31 1950 0CC7 0B18 206C 5AFD -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 232 bytes Desc: not available Url : http://shadowknight.real-time.com/pipermail/tclug-list/attachments/20011120/27cd7b6e/attachment.pgp