Docs For Class ProceduralPages

ProceduralPages

Description

Intermediate procedural page parsing structure.

This structure parses defines, functions, and global variables by file, and then iterates over the elements to document conflicts.

author: Greg Beaver <[email protected]>
version: Release: @VER@
copyright: 2002-2008 Gregory Beaver
link: http://pear.php.net/PhpDocumentor
link: http://www.phpdoc.org
todo: CS cleanup - change package to PhpDocumentor
since: 1.1
license: LGPL

Located in /phpDocumentor/ProceduralPages.inc (line 58)

Variable Summary

string $curfile

array $defineconflicts

array $definesbyfile

array $definesbynamefile

array $functionconflicts

array $functionsbyfile

array $functionsbynamefile

array $globalconflicts

array $globalsbyfile

array $globalsbynamefile

array $ignorepages

array $includesbyfile

array $pageclasspackages

array $pageconflicts

array $pagepackages

array $pages

array $pathpages

Method Summary

void addClassPackageToFile (string $file, string $package, string $subpackage)

void addDefine (parserDefine &$element)

void addFunction (parserFunction &$element)

void addGlobal (parserGlobal &$element)

void addInclude (parserInclude &$element)

void addPage (parserPage &$element)

void addPagePackage (string $path, string $package, string $subpackage)

array|bool getPathInfo (string $path, mixed &$c)

array|string getRealPath (string $path, string $file)

void ignorePage (parserPage &$element)

parserPage|bool pathMatchesParsedFile (string $path, string $infile)

void replaceElement (parserElement &$element)

void setName (string $name)

void setParseBase (mixed $pbase)

void setupPagePackages ()

void setupPages (phpDocumentor_IntermediateParser &$render)

Variables

string $curfile (line 67)

file being parsed, used in every add function to match up elements with the file that contains them

see: addClass(), addMethod(), addVar(), nextFile()

array $defineconflicts = array() (line 314)

Namespace conflicts within all documented packages of functions

Format:

     array(
         functionname => array(
             full path,
             full path,
             ...
         )
     )

array $definesbyfile = array() (line 157)

array of parsed defines organized by the full path of the file that contains the define.

Format:

     array(
         full path => array(
             definename => parserDefine
         )
     )

array $definesbynamefile = array() (line 211)

array of file names organized by defines that are in the file.

This structure is designed to handle name conflicts. Two files can contain defines with the same name, and this array will record both filenames to help control namespace errors Format:

     array(
         definename => array(
             full path of file containing definename,
             full path of file 2 containing definename,
             ...
         )
     )

array $functionconflicts = array() (line 282)

Namespace conflicts within all documented packages of functions

Format:

     array(
         functionname => array(
             full path,
             full path,
             ...
         )
     )

array $functionsbyfile = array() (line 142)

array of parsed functions organized by the full path of the file that contains the function.

Format:

     array(
         full path => array(
             functionname => parserFunction
         )
     )

array $functionsbynamefile = array() (line 192)

array of file names organized by functions that are in the file.

This structure is designed to handle name conflicts. Two files can contain functions with the same name, and this array will record both filenames to help control namespace errors Format:

     array(
         functionname => array(
             full path of file containing functionname,
             full path of file 2 containing functionname,
             ...
         )
     )

array $globalconflicts = array() (line 330)

Namespace conflicts within all documented packages of functions

Format:

     array(
         functionname => array(
             full path,
             full path,
             ...
         )
     )

array $globalsbyfile = array() (line 172)

array of parsed global variables organized by the full path of the file that contains the global variable definition.

Format:

     array(
         full path => array(
             globalname => parserGlobal
         )
     )

array $globalsbynamefile = array() (line 231)

array of file names organized by global variables that are in the file.

This structure is designed to handle name conflicts. Two files can contain global variables with the same name, and this array will record both filenames to help control namespace errors Format:

     array(
         global variablename => array(
             full path of file containing global variablename,
             full path of file 2 containing global variablename,
             ...
         )
     )

array $ignorepages = array() (line 100)

array of all procedural pages ordered by name

that have been ignored via -po or @access private or @ignore Format:

     array(
         name => array(
             fullpath => parserPage,
             fullpath => parserPage2 [if there are name conflicts],
             ...
         )
     )

array $includesbyfile = array() (line 127)

array of parsed includes organized by the full path of the file that contains the include.

Format:

     array(
         full path => array(
             includename => parserInclude
         )
     )

array $pageclasspackages = array() (line 266)

array of packages assigned to classes in a file, ordered by fullpath

Format:

     array(
         fullpath => array(
             packagename => array(
                 subpackagename => 1,
                 subpackagename => 1,
                 ..
             ),
             packagename2 => array(...
             )
         )
     )

array $pageconflicts = array() (line 298)

Namespace conflicts within all documented pages

Format:

     array(
         pagename => array(
             fullpath,
             fullpath,
             ...
         )
     )

array $pagepackages = array() (line 246)

array of packages ordered by full path

Format:

     array(
         fullpath => array(
             packagename,
             subpackagename
         )
     )

array $pages = array() (line 83)

array of all procedural pages ordered by name

Format:

     array(
         name => array(
             fullpath => parserPage,
             fullpath => parserPage2 [if there are name conflicts],
             ...
         )
     )

array $pathpages = array() (line 112)

array of all procedural page names ordered by full path to the file

Format:

     array(
         fullpath => name
     )

Methods

addClassPackageToFile (line 613)

adds a package from a class to the current file

void addClassPackageToFile (string $file, string $package, string $subpackage)

string $file: full path to the file that contains the class
string $package: package name
string $subpackage: subpackage name

addDefine (line 552)

sets up the $definesbyfile array using $curfile

void addDefine (parserDefine &$element)

parserDefine &$element: the "define" element

addFunction (line 508)

sets up the $functionsbyfile array using $curfile

void addFunction (parserFunction &$element)

parserFunction &$element: the "function" object

addGlobal (line 530)

sets up the $globalsbyfile array using $curfile

void addGlobal (parserGlobal &$element)

parserGlobal &$element: the "global" element

addInclude (line 496)

sets up the $includesbyfile array using $curfile

void addInclude (parserInclude &$element)

parserInclude &$element: the "include" element object

addPage (line 349)

sets up the $pages array

void addPage (parserPage &$element)

parserPage &$element: the parser page element

addPagePackage (line 450)

Changes the package of the page represented by $path

changes package in both the $pages array and the pagepackages array

void addPagePackage (string $path, string $package, string $subpackage)

string $path: full path
string $package: the package name
string $subpackage: the subpackage name

getPathInfo (line 385)

gathers path-related info about a given element

return: an array of path info, or FALSE
todo: figure out what &$c is and update the param tag

array|bool getPathInfo (string $path, mixed &$c)

string $path: path to the element
mixed &$c: ???

getRealPath (line 1033)

Ensures the path to the file is an absolute path

return: returns an array of possible file locations or a string if there is an exact match

array|string getRealPath (string $path, string $file)

string $path: path to the file
string $file: the file name

ignorePage (line 368)

moves a page from the $pages array to the $ignorepages array

void ignorePage (parserPage &$element)

parserPage &$element: the parser page element

pathMatchesParsedFile (line 983)

checks to see if the parsed file matches the given path

return: matched parserPage if found, or FALSE if not found

parserPage|bool pathMatchesParsedFile (string $path, string $infile)

string $path: the path to look for
string $infile: the file to check

replaceElement (line 575)

Used to align an element with the package of its parent page prior to Conversion.

void replaceElement (parserElement &$element)

parserElement &$element: the element to align

setName (line 421)

Change a page's name from its file to alias $name

This function is used to handle a @name tag in a page-level DocBlock

void setName (string $name)

string $name: the alias

setParseBase (line 969)

sets the parser base

void setParseBase (mixed $pbase)

mixed $pbase: the parser base

setupPagePackages (line 628)

if there is one class package in a file, the parent path inherits the package if its package is default.

helps with -po to avoid dumb bugs

void setupPagePackages ()

setupPages (line 911)

Adjusts packages of all pages and removes name conflicts within a package

Automatic linking requires that each linkable name have exactly one element associated with it. In other words, there cannot be two functions named foo() in the same package.

This also adheres to php rules with one exception:

if ($test == 3) {
define('whatever', 'this thing');
} else {
define('whatever', 'this other thing');
}

phpDocumentor is not aware of conditional control structures because it would slow things down considerably. So, what phpDocumentor does is automatically ignore the second define and raise a warning. The warning can be eliminated with an @ignore tag on the second element like so:

if ($test == 3) {
define('whatever', 'this thing');
} else {
/**
* @ignore
*/
define('whatever', 'this other thing');
}

If there are two files that contain the same procedural elements in the same package (for example, a common configuration file common.php), they will also be ignored as if they were in the same file. The reasoning behind this is simple. A package is an indivisible set of files and classes that a user will include in their code. Name conflicts must be avoided to allow successful execution.

This function also plays the all-important role of calling phpDocumentor_IntermediateParser::addElementToPage() in order to add processed elements to their pages for Conversion.

void setupPages (phpDocumentor_IntermediateParser &$render)

phpDocumentor_IntermediateParser &$render: the parser

Documentation generated on Mon, 05 Dec 2011 21:40:20 -0600 by phpDocumentor 1.4.4