php.net |  support |  documentation |  report a bug |  advanced search |  search howto |  statistics |  random bug |  login

go to bug id or search bugs for

Request #71528 Warnings for short_open_tag
Submitted: 2016-02-05 06:58 UTC Modified: 2017-08-04 23:06 UTC
Votes:2
Avg. Score:4.5 ± 0.5
Reproduced:2 of 2 (100.0%)
Same Version:2 (100.0%)
Same OS:2 (100.0%)
From: php dot net at shwups dot ch Assigned:
Status: Suspended Package: *General Issues
PHP Version: 7.0.3 OS: all
Private report: No CVE-ID: None
View Add Comment Developer Edit
Welcome back! If you're the original bug submitter, here's where you can edit the bug or add additional notes.
If this is not your bug, you can add a comment by following this link.
If this is your bug, but you forgot your password, you can retrieve your password here.
Password:
Status:
Package:
Bug Type:
Summary:
From: php dot net at shwups dot ch
New email:
PHP Version: OS:

 

 [2016-02-05 06:58 UTC] php dot net at shwups dot ch 
Description:
------------
I would like the opportunity to get warnings for short_open_tags.

It would be much easier for developers to rearrange their code from using short_open_tags to not using it.


Something like 

error_reporting(E_RECOMMENDED);

would be great!

Patches

Add a Patch

Pull Requests

Add a Pull Request

History

AllCommentsChangesGit/SVN commitsRelated reports
 [2016-11-30 18:48 UTC] cmb@php.net 
This feature would require an RFC[1], so I'm suspending this ticket.

[1] <https://wiki.php.net/rfc/howto>
 [2017-08-04 23:06 UTC] stas@php.net
-Status: Open +Status: Suspended
 [2017-08-04 23:06 UTC] stas@php.net 
Thank you for your interest in PHP and for submitting a feature request. Please be aware that due to the magnitude of change this request requires, it would be necessary to discuss it on PHP Internals list (internals@lists.php.net) as an RFC. Please read the guide about creating RFCs here:
https://wiki.php.net/rfc/howto
If you haven't had experience with writing RFCs before, it is advised to seek guidance on the Internals list (http://php.net/mailing-lists.php) and/or solicit help from one of the experienced developers. 

Please to not consider this comment as a negative view on the merits of your proposal - every proposal which requires changes of certain magnitude, even the very successful and widely supported ones, must be done through the RFC process. This helps make the process predictable, transparent and accessible to all developers.
 
PHP Copyright © 2001-2024 The PHP Group
All rights reserved. 		Last updated: Thu Apr 25 01:01:30 2024 UTC