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 <ka...@php.net> wrote: > Hi > > 2016-08-28 5:07 GMT+02:00 Rene Veerman <rene.veerman.netherla...@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 > ka...@php.net >
