> This note from Derick pretty much reflects the idea... it makes sense: > <quote> > I see that renaming the CGI to php-cgi might break things indeed, and > that's never a good idea. But so is changing the name of the CLI (php) > to something else. It also breaks things, not only for me, but also for > countless others using the CLI with the name 'php'. We also need to > think about these users as well. This leaves my opinion that i'm -1 on > renaming the CLI to something else, and i'm a -0 (yes this changed :) on > renaming the CGI. This leaves the (IMO) only possible solution: > integrate them back into one binary and adding some magic which triggers > CLI or CGI mode (perhaps to check for some environment variable). > </quote> >
Hrmm, how does renaming php-cli break compatibility between PHP _releases_? -Sterling > > On Wed, 2002-12-18 at 14:59, Andrei Zmievski wrote: > > What was the consensus on CGI vs. CLI naming or merging issue? Or was > > there a consensus at all? I full plan to go ahead with 4.3.0 release > > before the end of the year, so those interested in doing anything about > > this issue better get their butts in gear. > > > > -Andrei http://www.gravitonic.com/ > > > > "This isn't right. This isn't even wrong." > > -- Wolfgang Pauli > -- > Xavier Spriet <[EMAIL PROTECTED]> > > > -- > PHP Development Mailing List <http://www.php.net/> > To unsubscribe, visit: http://www.php.net/unsub.php > -- PHP Development Mailing List <http://www.php.net/> To unsubscribe, visit: http://www.php.net/unsub.php
