ID:               16234
 Updated by:       [EMAIL PROTECTED]
 Reported By:      adam at adeptsoftware dot com
-Status:           Open
+Status:           Closed
 Bug Type:         Documentation problem
 Operating System: WinXP
 PHP Version:      4.1.2
 New Comment:

These sections now exist and will show up during the next manual build.
 They use <sect2> instead of <sect1> as it seems more appropriate this
way.

http://cvs.php.net/cvs.php/phpdoc/en/language/variables.xml

Thanks for the report :)


Previous Comments:
------------------------------------------------------------------------

[2002-03-25 04:00:44] [EMAIL PROTECTED]

For global and static to appear in the CHM index,
and be used as php.net/global, these two keywords
should have their own pages in the manual (eg. sect1.)

Reopening,
Goba

------------------------------------------------------------------------

[2002-03-24 11:24:53] adam at adeptsoftware dot com

I should have mentioned, I'm referring to the index of the CHM.  The
CHM people said to post it here because it was content related..?

------------------------------------------------------------------------

[2002-03-24 06:10:06] [EMAIL PROTECTED]

"global" as well as "static" are listed in the "List of Keywords"
(http://at.php.net/manual/en/reserved.php), and are described in the
Language Reference (exactly Variable Scope,
http://at.php.net/manual/en/language.variables.scope.php), which is
also linked from the Keyword-list.


------------------------------------------------------------------------

[2002-03-23 11:49:07] adam at adeptsoftware dot com

There is no page for the keywords "global" or "static".
Neither can be found in the index. There are many things
like this that are only mentioned in passing, without
having an actual definition.


------------------------------------------------------------------------


-- 
Edit this bug report at http://bugs.php.net/?id=16234&edit=1


-- 
PHP Documentation Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php

Reply via email to