Bug #75980 [Com]: greater or equal (formerly >=) is missinterpreted

From: Date: Mon, 19 Feb 2018 13:45:59 +0000
Subject: Bug #75980 [Com]: greater or equal (formerly >=) is missinterpreted
References: 1  Groups: php.bugs 
Request: Send a blank email to php-bugs+get-214038@lists.php.net to get a copy of this message
Edit report at https://bugs.php.net/bug.php?id=75980&edit=1 ID: 75980 Comment by: spam2 at rhsoft dot net Reported by: rolf at rolfjentsch dot de Summary: greater or equal (formerly >=) is missinterpreted Status: Not a bug Type: Bug Package: Scripting Engine problem Operating System: windows 10 xamp PHP Version: 7.2.2 Block user comment: N Private report: N New Comment: > The german documentation does not say that <? is deprecated it's widely known for around 10 years that you shouldn't rely on this mis-feature you initial problem with the statement ">= finish interpreting" was that you where not capable to realize that PHP don't get executed at all and the whole source was sent to the client https://softwareengineering.stackexchange.com/questions/151661/is-it-bad-practice-to-use-tag-in-php Previous Comments: ------------------------------------------------------------------------ [2018-02-19 13:38:30] rolf at rolfjentsch dot de The german documentation does not say that <? is deprecated or should not be used see http://php.net/manual/de/language.basic-syntax.phptags.php. May be that page should be updated ... beside that my provider has it enabled and so i enabled the short tags on my development server as well. So i can only thank you for your advice. ------------------------------------------------------------------------ [2018-02-19 13:22:36] cmb@php.net Besides what nikic said: if you're experiencing such strange behavior again, have a look at the generated HTML source code! ------------------------------------------------------------------------ [2018-02-19 13:22:31] spam2 at rhsoft dot net > well to make it a final the problem only arrises when i > start my php section with <?. > it does not occur when i start it with <?php well, to make it final: that's why you should not mix different issues in one bugreport and hence your broken snippet has alos no place in https://bugs.php.net/bug.php?id=73232 http://php.net/manual/en/ini.core.php#ini.short-open-tag <? is short-open-tags which defaults for years now to disabled that it worked in some configuration with 5.6 was because someone enabled it you can build PHP7 with --disable-short-tags and that's what you see because you ignored that many years that you shold write <?php and not <? but as said: this "issue" which is none has no place in that bugreport which is about something cmpletly differnt at all ------------------------------------------------------------------------ [2018-02-19 13:18:34] nikic@php.net Please check your "short_open_tag" ini setting. You have it enabled on PHP 5 and disabled on PHP 7. ------------------------------------------------------------------------ [2018-02-19 13:18:29] jhdxr@php.net Thank you for taking the time to write to us, but this is not a bug. Please double-check the documentation available at http://www.php.net/manual/ and the instructions on how to report a bug at http://bugs.php.net/how-to-report.php > But a if(strpos($_SERVER['SERVER_ADDR'],"192.168.10") !< 0) still does > what it does in previous versions !< is an invalid operator in PHP, please double check the manual (http://php.net/manual/en/language.operators.php) before you try to create something. btw, rhsoft has already point out that you should read the manual to see how strpos works, especially the warning message in red box. ------------------------------------------------------------------------ The remainder of the comments for this report are too long. To view the rest of the comments, please view the bug report online at https://bugs.php.net/bug.php?id=75980 -- Edit this bug report at https://bugs.php.net/bug.php?id=75980&edit=1

« previous php.bugs (#214038) next »