get_included_files(3) [php man page]

GET_INCLUDED_FILES(3)							 1						     GET_INCLUDED_FILES(3)

get_included_files - Returns an array with the names of included or required files

SYNOPSIS

       array get_included_files (void  )

DESCRIPTION

	Gets the names of all files that have been included using include(3), include_once(3), require(3) or require_once(3).

RETURN VALUES

	Returns an array of the names of all files.

	The  script  originally called is considered an "included file," so it will be listed together with the files referenced by include(3) and
       family.

	Files that are included or required multiple times only show up once in the returned array.

EXAMPLES

       Example #1

	      get_included_files(3) example

	      <?php
	      // This file is abc.php

	      include 'test1.php';
	      include_once 'test2.php';
	      require 'test3.php';
	      require_once 'test4.php';

	      $included_files = get_included_files();

	      foreach ($included_files as $filename) {
		  echo "$filename
";
	      }

	      ?>

	      The above example will output:

	      abc.php
	      test1.php
	      test2.php
	      test3.php
	      test4.php

NOTES

       Note

	       Files included using the auto_prepend_file configuration directive are not included in the returned array.

SEE ALSO

       include(3), include_once(3), require(3), require_once(3), get_required_files(3).

PHP Documentation Group 												     GET_INCLUDED_FILES(3)

RUNKIT_SANDBOX_PARENT(3)						 1						  RUNKIT_SANDBOX_PARENT(3)

Runkit_Sandbox_Parent - Runkit Anti-Sandbox Class

SYNOPSIS

       void Runkit_Sandbox_Parent::__construct (void  )

DESCRIPTION

	Instantiating  the Runkit_Sandbox_Parent class from within a sandbox environment created from the Runkit_Sandbox class provides some (con-
       trolled) means for a sandbox child to access its parent.

       Note

	      Sandbox support (required for runkit_lint(3), runkit_lint_file(3), and the Runkit_Sandbox class) is only available as of	PHP  5.1.0
	      or  specially  patched  versions	of PHP 5.0, and requires that thread safety be enabled. See the README file included in the runkit
	      package for more information.

	In order for any of the Runkit_Sandbox_Parent features to function. Support must be enabled on a per-sandbox basis by  enabling  the  par-
       ent_access flag from the parent's context.

       Example #1

	      Working with variables in a sandbox

	      <?php
	      $sandbox = new Runkit_Sandbox();
	      $sandbox['parent_access'] = true;
	      ?>

ACCESSING THE PARENT'S VARIABLES
	Just  as  with	sandbox  variable  access,  a sandbox parent's variables may be read from and written to as properties of the Runkit_Sand-
       box_Parent class. Read access to parental variables may be enabled with the parent_read setting (in addition to the base parent_access set-
       ting). Write access, in turn, is enabled through the parent_write setting.

	Unlike	sandbox child variable access, the variable scope is not limited to globals only. By setting the parent_scope setting to an appro-
       priate integer value, other scopes in the active call stack may be inspected instead. A value of 0 (Default) will direct variable access at
       the global scope. 1 will point variable access at whatever variable scope was active at the time the current block of sandbox code was exe-
       cuted. Higher values progress back through the functions that called the functions that led to the sandbox executing  code  that  tried	to
       access its own parent's variables.

       Example #2

	      Accessing parental variables

	      <?php
	      $php = new Runkit_Sandbox();
	      $php['parent_access'] = true;
	      $php['parent_read'] = true;

	      $test = "Global";

	      $php->eval('$PARENT = new Runkit_Sandbox_Parent;');

	      $php['parent_scope'] = 0;
	      one();

	      $php['parent_scope'] = 1;
	      one();

	      $php['parent_scope'] = 2;
	      one();

	      $php['parent_scope'] = 3;
	      one();

	      $php['parent_scope'] = 4;
	      one();

	      $php['parent_scope'] = 5;
	      one();

	      function one() {
		  $test = "one()";
		  two();
	      }

	      function two() {
		  $test = "two()";
		  three();
	      }

	      function three() {
		  $test = "three()";
		  $GLOBALS['php']->eval('var_dump($PARENT->test);');
	      }
	      ?>

       The above example will output:

       string(6) "Global"
       string(7) "three()"
       string(5) "two()"
       string(5) "one()"
       string(6) "Global"
       string(6) "Global"

CALLING THE PARENT'S FUNCTIONS
	Just  as  with	sandbox  access, a sandbox may access its parents functions providing that the proper settings have been enabled. Enabling
       parent_call will allow the sandbox to call all functions available to the parent scope. Language constructs are each  controlled  by  their
       own  setting:  print(3)	and  echo(3) are enabled with parent_echo. die(3) and exit(3) are enabled with parent_die. eval(3) is enabled with
       parent_eval while include(3), include_once(3), require(3), and require_once(3) are enabled through parent_include.

PHP Documentation Group 												  RUNKIT_SANDBOX_PARENT(3)