Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:106445 Return-Path: Delivered-To: mailing list internals@lists.php.net Received: (qmail 75126 invoked from network); 8 Aug 2019 18:29:30 -0000 Received: from unknown (HELO cache4.mydevil.net) (213.189.55.195) by pb1.pair.com with SMTP; 8 Aug 2019 18:29:30 -0000 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=korulczyk.pl; s=devil; h=Content-Transfer-Encoding:Content-Type:In-Reply-To :MIME-Version:Date:Message-ID:From:References:To:Subject:Sender:Reply-To:Cc: Content-ID:Content-Description:Resent-Date:Resent-From:Resent-Sender: Resent-To:Resent-Cc:Resent-Message-ID:List-Id:List-Help:List-Unsubscribe: List-Subscribe:List-Post:List-Owner:List-Archive; bh=XaNCFOSwR9hAbvf44pw6DuaGZiDbZu1mlm2HjHzMZQM=; b=Eq6rzwd9IiGDyHtaQEVSCs+Fnl jYzD3INbsFnPxzuVfjBJh7lZdJxMWEQXf+236RUzE5YAXjHrqPef+CA35XGqcsjMvojSkltpgkdQA eAddNUwVbZNgPsdH9iKM2zNxp5rzIjtGlishx1Imwq9kmQWShcv/n/9kT9e0LF7Q8VMw=; To: internals@lists.php.net References: <1759114.DMe9nKvMbn@mcmic-probook> <62c73b8f-df41-43c2-bb51-ceeaf607cacf@Spark> Message-ID: <5d6447fe-ab87-bf30-49fe-fecff7062ffe@korulczyk.pl> Date: Thu, 8 Aug 2019 17:56:39 +0200 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.8.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit X-AV-Check: Passed X-System-Sender: robert@korulczyk.pl Subject: Re: [PHP-DEV] [RFC] [VOTE] Deprecate PHP's short open tags, again From: robert@korulczyk.pl (Robert Korulczyk) > Many people have talked about the potential impacts of keeping short tags. > I have yet to see anyone give an actual example where they have been > negatively impacted by their existence. I've given you my personal story of > how removing them will negatively impact my company. I welcome anyone that > can provide an actual incident where the existence of short tags hurt them, > or, the continued existence is likely to have a large negative impact on > them in the future. I was bitten by short open tags. Despite the "no short open tag" policy in our app, one occurrence of `