Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:13526
Return-Path: <kameshj@fastmail.fm>
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Delivered-To: mailing list internals@lists.php.net
Received: (qmail 10094 invoked by uid 1010); 26 Oct 2004 15:31:22 -0000
Delivered-To: ezmlm-scan-internals@lists.php.net
Delivered-To: ezmlm-internals@lists.php.net
Received: (qmail 10065 invoked from network); 26 Oct 2004 15:31:21 -0000
Received: from unknown (HELO out2.smtp.messagingengine.com) (66.111.4.26)
  by pb1.pair.com with SMTP; 26 Oct 2004 15:31:21 -0000
Received: from web1.messagingengine.com (web1.internal [10.202.2.210])
	by frontend1.messagingengine.com (Postfix) with ESMTP id F3B58C34658;
	Tue, 26 Oct 2004 11:31:20 -0400 (EDT)
Received: by web1.messagingengine.com (Postfix, from userid 99)
	id 7B47027FB; Tue, 26 Oct 2004 11:31:21 -0400 (EDT)
Content-Disposition: inline
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="iso-8859-1"
MIME-Version: 1.0
X-Mailer: MIME::Lite 1.5  (F2.73; T1.001; A1.64; B3.05; Q3.03)
Cc: "Wez Furlong" <kingwez@gmail.com>, internals@lists.php.net,
	helly@php.net, edink@php.net
References: <1098796701.32385.207284415@webmail.messagingengine.com>
   <4e89b42604102607014c368073@mail.gmail.com>
   <1098801076.10214.207288490@webmail.messagingengine.com>
   <417E6C13.6070608@caraveo.com>
In-Reply-To: <417E6C13.6070608@caraveo.com>
To: "Shane Caraveo" <shane@caraveo.com>
Date: Tue, 26 Oct 2004 08:31:21 -0700
X-Sasl-Enc: DMSqO+nkiV+mIBK9HG4Chg 1098804681
Message-ID: <1098804681.17355.207295784@webmail.messagingengine.com>
Subject: Re: [PHP-DEV] Can someone allocate 2 command line switches for php cli 
    on NetWare?
From: kameshj@fastmail.fm ("Kamesh Jayachandran")

Shane,

This solution seems interesting.

I will give a try.

With regards
Kamesh Jayachandran
On Tue, 26 Oct 2004 08:24:03 -0700, "Shane Caraveo" <shane@caraveo.com>
said:
> Here is my suggestion,
> Rather than taking two switches, php should grow a generic switch for 
> this kind of use:
> 
> php -o param:value;param:value;
> 
> This allows custom mods to php a way to introduce new options that are 
> not part of the general php distribution, without the need to land grab 
> the limited switches.  There is also the potential for someone to 
> develop an extension to allow a php script to handle some alternative 
> switches.
> 
> Regards,
> Shane
> 
> Kamesh Jayachandran wrote:
> > Still we need to have switches to have this interactivity or not(Based
> > on usage regular/cron)
> > We need one more switch to determine whether to have output in the
> > Logger screen(System wide log console) or Interpreter screen.