Home >Backend Development >PHP Tutorial >What are the changes in the global variable mechanism (global invalid error) in PHP5 and PHP7 versions? (Code actual test)

What are the changes in the global variable mechanism (global invalid error) in PHP5 and PHP7 versions? (Code actual test)

藏色散人
藏色散人Original
2019-01-09 13:44:503003browse

For PHP programmers, as different versions of PHP update and improve some function variable mechanisms, people often become confused when using the same variable in different versions produces different results. So this article mainly explains to you in detail why different results occur when using the same global variable under PHP5 and PHP7 versions? Let me give you a simple and easy-to-understand example.

For example, the existing exl.php page operation code is as follows:

What are the changes in the global variable mechanism (global invalid error) in PHP5 and PHP7 versions? (Code actual test)

#The result we ran in the local php5 version environment is 5, as shown in the screenshot below :

What are the changes in the global variable mechanism (global invalid error) in PHP5 and PHP7 versions? (Code actual test)

Then the result of running it in the php7 version environment is 3, as shown in the screenshot below:

What are the changes in the global variable mechanism (global invalid error) in PHP5 and PHP7 versions? (Code actual test)

The reason why Different operation results will appear. This is actually because in the latest php7 version, the PHP global variable processing mechanism has been modified. In this version, the global keyword can now only refer to simple variables. So when we operate in the local php5 version environment, the output value of $y is $x $y=5. At this time, global is equivalent to the use of global variables. In the php7 environment, the output value of $y is $y=3. At this time, the global variable can only directly reference the simple variable $y.

So through the above sample code explanation, I hope that this article about the problem of global variables in PHP producing different results when operating in different versions will be helpful to everyone when encountering related problems. I also hope that everyone can pass this article. This article provides an understanding of the usage of php global under different versions.


A brief introduction, what is the PHP global variable global? First of all, the phpglobal scope does not apply to the entire website, but to the current page, including all files in include or require. However, global variables defined within the function body can be used within the function body, while global variables defined outside the function body cannot be used within the function body.

I also mention here that the php $GLOBALS variable refers to all variables available in the global scope. In the $GLOBALS array, each variable is an element, the key name corresponds to the variable name, and the value corresponds to the variable's content. . $GLOBALS exists in the global scope because $GLOBALS is a superglobal variable. Pay attention to the writing method of $GLOBALS. For example, the variable $a1 is written as $GLOBALS[‘a1’].

Then let’s use a simple and easy-to-understand example to explain in detail the problem that global is invalid in php:

First, the demo1.php page code is as follows:

<?php
    $site_name = &#39;CodePlayer&#39;;
    function sayHi(){
        global $site_name;
        echo "Hello! Welcome to $site_name !";
    }
    ?>

The demo2.php page code is as follows:

<?php
    function include_view_page(){
        include &#39;demo2.php&#39;;
        sayHi();                   
    }
    include_view_page();
    ?>

When we visit the demo1.php page, the welcome statement can be displayed correctly. However, when we use the browser to access the demo2.php page, the output result is as follows:

Hello! Welcome to !

When we call the sayHi() function in the function include_view_page(), the global $site_name in the sayHi() function of the demo2.php page But it was not correctly recognized and took effect.

In fact, when we include the demo2.php page in the function include_view_page(), the variable $site_name of the demo2.php page is equivalent to being stored in the scope within the include_view_page() function. Everyone knows that global a variable within a function actually establishes a reference to the global variable of the page within the function. In this example, the $site_name variable is only a local variable within the include_view_page() function for demo1.php, so the global variable cannot be displayed. When we make related calls, we cannot obtain the correct variables and variable values.

In PHP, we especially need to pay attention to the above-mentioned problem of including a page within a function, causing the scope of the variables in the page to change. In order to avoid this situation, we should try to reduce multi-level include calls and try not to use include within functions. In addition, we can also declare $site_name as a global variable in the demo2.php page.

//demo2.php
    <?php
    global $site_name;
    $site_name = &#39;CodePlayer&#39;;
    function sayHi(){
        global $site_name;
        echo "Hello! Welcome to $site_name !";
    }
    ?>

An example of how to reference global variables in a function is as follows:

What are the changes in the global variable mechanism (global invalid error) in PHP5 and PHP7 versions? (Code actual test)

The output result is as follows:

var2 is set to 'xxxxxx'
var2 is set to 'eeee'

is visible, in the above code:
$var2 =&$var1; //1 is only visible inside the function. And $GLOBALS["var2"] =&$var1; //2 is visible in the global scope.

I hope this article will help everyone about the invalid problem of php global!

The above is the detailed content of What are the changes in the global variable mechanism (global invalid error) in PHP5 and PHP7 versions? (Code actual test). For more information, please follow other related articles on the PHP Chinese website!

Statement:
The content of this article is voluntarily contributed by netizens, and the copyright belongs to the original author. This site does not assume corresponding legal responsibility. If you find any content suspected of plagiarism or infringement, please contact admin@php.cn

Related articles

See more