Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:16266 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 4267 invoked by uid 1010); 17 May 2005 14:24:02 -0000 Delivered-To: ezmlm-scan-internals@lists.php.net Delivered-To: ezmlm-internals@lists.php.net Received: (qmail 85321 invoked from network); 17 May 2005 14:09:28 -0000 Received: from unknown (HELO gmail.com) (127.0.0.1) by localhost with SMTP; 17 May 2005 14:09:28 -0000 X-Host-Fingerprint: 64.233.184.199 wproxy.gmail.com Linux 2.4/2.6 Received: from ([64.233.184.199:2210] helo=wproxy.gmail.com) by pb1.pair.com (ecelerity 1.2 r(5656M)) with SMTP id 4B/C0-01538-81BF9824 for ; Tue, 17 May 2005 10:09:28 -0400 Received: by wproxy.gmail.com with SMTP id 57so1828128wri for ; Tue, 17 May 2005 07:09:24 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=Y9+F+c69lTsWUaCa0tZ5MdDlKIwIdEIAXrW6x0q1/z9ZeRT2sO4Y9BDTJ5Bgw6tgWtgYjIf8dG/mFNmdRth1mpX1V28zWOGw3Hg1x9g72G0erw+b/33BVOL6e5dslHJtrfjq2toxqgFuEGSGK2kJaO2IsXM14BthsuFcOm45TAE= Received: by 10.54.141.10 with SMTP id o10mr4431149wrd; Tue, 17 May 2005 07:09:24 -0700 (PDT) Received: by 10.54.77.4 with HTTP; Tue, 17 May 2005 07:09:24 -0700 (PDT) Message-ID: <4e89b426050517070932202006@mail.gmail.com> Date: Tue, 17 May 2005 10:09:24 -0400 Reply-To: Wez Furlong To: Blake Matheny Cc: Derick Rethans , George Schlossnagle , PHP Developers Mailing List In-Reply-To: <4289DDBA.8020809@3gupload.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: <4288F183.7010804@3gupload.com> <4289DDBA.8020809@3gupload.com> Subject: Re: [PHP-DEV] Patch for php_error_cb From: kingwez@gmail.com (Wez Furlong) On 5/17/05, Blake Matheny wrote: > - No need to add an extension every time you upgrade PHP But you still need to write a custom shared library, so this is not such a great point. > - No additional patching (which an extension essentially requires) But you still need to write a custom shared library. > - Only adds a couple of extra operations (no performance hit) > - Backwards compatible with existing php.ini I don't think those two points are relevant. > - Possibility for other prefixes (script:,file:,socket:,etc) This is the only plus point in your argument, but you should consider that we already have a mechanism for logging to files, and no one has asked to be able to log to anything else for quite some time. I think you really need to do some convincing to get the patch in, and I don't see many benefits to the majority of PHP users with the patch as it stands now. --Wez.