> -----Original Message----- > From: Zeev Suraski [mailto:[EMAIL PROTECTED]] > Sent: 11 December 2002 12:15 > > Guys, fact is that it doesn't matter that much what this binary is > called. We can call it bhb for all practical purposes (not that I'm > suggesting that). People will get used to whatever it's named.
If it were me (which, of course, it isn't, but...), I'd leave the cgi as php and call the command-line version phpc. (Well, actually, if it were *just* me, I'd leave them both as php -- even on Windows -- and just make sure I had them in appropriate directories, but I'm extremely aware that real-world users are often not up to that kind of subtlety.) What I absolutely would *not* do is rename the cgi version to php-cgi whilst *simultaneously* introducing a new php with a different purpose. If I were going to do this, I'd want to do it in steps: 1 - cgi to php-cgi + introduce php-cli (so any installations still looking for php get a straight file not found); 2 - php-cli to php. As I'm pretty sure this isn't going to fly, let's go back to my first para...!! Cheers! Mike --------------------------------------------------------------------- Mike Ford, Electronic Information Services Adviser, Learning Support Services, Learning & Information Services, JG125, James Graham Building, Leeds Metropolitan University, Beckett Park, LEEDS, LS6 3QS, United Kingdom Email: [EMAIL PROTECTED] Tel: +44 113 283 2600 extn 4730 Fax: +44 113 283 3211 -- PHP Development Mailing List <http://www.php.net/> To unsubscribe, visit: http://www.php.net/unsub.php
