Newsgroups: php.general,php.internals
Path: news.php.net
Xref: news.php.net php.general:325720 php.internals:95491
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.220.174 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <CAJW__o2oYckLdH2VoegAWgPu3aWJx2sO_Z6UT9WKh_TY44tkhQ@mail.gmail.com>
References: <CACMzB5dg_00rSMxhOugBFNcKHLOunV5=gMMHf-P_YJoBqjr-aQ@mail.gmail.com>
 <CAJW__o2oYckLdH2VoegAWgPu3aWJx2sO_Z6UT9WKh_TY44tkhQ@mail.gmail.com>
Date: Sun, 28 Aug 2016 07:09:25 +0200
Message-ID: <CACMzB5d9pqi+jxPHTajLo4A02fAm6s-edC_=bdzJ4fbON=sOkA@mail.gmail.com>
To: Kalle Sommer Nielsen <kalle@php.net>
Cc: php-general@lists.php.net, Internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary=001a1148733a8c6bbf053b1ac183
Subject: Re: [PHP-DEV] feature-request : html + css logging in apache logs
 (example for the rest of the unix community too)
From: rene.veerman.netherlands@gmail.com (Rene Veerman)

--001a1148733a8c6bbf053b1ac183
Content-Type: text/plain; charset=UTF-8

Thank you.

I'm not insisting it become the default, just thought it'd be handy..

As for the RFC, i'll do it after a nice long nap OK :)
I dont know anything about the internals of PHP, i'm a PHP + HTML developer
exclusively, but i'll try to give you some implementation suggestions in
what i can make of that RFC..

On Sun, Aug 28, 2016 at 5:56 AM, Kalle Sommer Nielsen <kalle@php.net> wrote:

>  Hi
>
> 2016-08-28 5:07 GMT+02:00 Rene Veerman <rene.veerman.netherlands@gmail.com
> >:
> > <snip>
> > it would really cut my development time in more than half if you could
> add
> > "all of this" (it's deadsimple and a few hours work imo) to the next
> > versions of PHP (and please make it the default, you can include sample
> CSS
> > or read in a CSS file that you set in php.ini (comment on how to do this
> in
> > the logfile html please))..
>
> The best way to accomplish this is to make an RFC[1], detailing this
> carefully, in a well-phrased manner.
>
> Side note here, despite it may be "deadsimple", it may not be so
> simple to just change PHP to act as you want in the next release, PHP
> is used by hundreds of millions, this means that anything that can
> change PHP's behavior must be analyzed, and it is very rarely we do
> such changes in minor releases. This means that the next release, if
> you write an RFC, should target PHP 7.2.0.
>
> For a feature like you propose, or as to how I read it, it would most
> likely never become default, but if it did get implemented in PHP, it
> would most likely be an opt-in feature. Sorry, but it is the harsh
> reality.
>
>
> Again, like mentioned on the php-general@ list, please keep to the
> mailing list rules, as linked in regards to top posting, and please do
> not embed huge chunks of code into mails, send a link to a paste bin
> instead, it makes the code rather hard to read and understand
> properly. Thanks
>
>
> [1] http://wiki.php.net/rfc
>
>
> --
> regards,
>
> Kalle Sommer Nielsen
> PHP Core Developer
> kalle@php.net
>

--001a1148733a8c6bbf053b1ac183--