...

...

@@ -1,10 +1,10 @@

1

1

<?xml version="1.0" encoding="utf-8"?>

2

2

<!-- $Revision$ -->

3

3

4

-

<phpdoc:varentry xmlns:phpdoc="http://php.net/ns/phpdoc" xml:id="language.variables.superglobals" xmlns="http://docbook.org/ns/docbook" xmlns:xlink="http://www.w3.org/1999/xlink" role="noversion">

4

+

<refentry role="variable" xml:id="language.variables.superglobals" xmlns="http://docbook.org/ns/docbook" xmlns:xlink="http://www.w3.org/1999/xlink" annotations="verify_info:false">

5

5

<refnamediv>

6

6

<refname>Superglobals</refname>

7

-

<refpurpose>Superglobals are built-in variables that are always available in all scopes</refpurpose>

7

+

<refpurpose>Built-in variables that are always available in all scopes</refpurpose>

8

8

</refnamediv>

9

9

10

10

<refsect1 role="description">

...

...

@@ -43,19 +43,6 @@

43

43

</para>

44

44

</note>

45

45

<note>

46

-

<title>Dealing with register_globals</title>

47

-

<para>

48

-

If the deprecated <link linkend="ini.register-globals">register_globals</link>

49

-

directive is set to <literal>on</literal> then the variables within will

50

-

also be made available in the global scope of the script. For example,

51

-

<varname>$_POST['foo']</varname> would also exist as <varname>$foo</varname>.

52

-

</para>

53

-

<para>

54

-

For related information, see the FAQ titled

55

-

"<link linkend="faq.register-globals">How does register_globals affect me?</link>"

56

-

</para>

57

-

</note>

58

-

<note>

59

46

<title>Variable variables</title>

60

47

<para>

61

48

Superglobals cannot be used as

...

...

@@ -76,7 +63,7 @@

76

63

</para>

77

64

</refsect1>

78

65

79

-

</phpdoc:varentry>

66

+

</refentry>

80

67

81

68

<!-- Keep this comment at the end of the file

82

69

Local variables:

83

70