PHP Wiki

benchmark

Anonymous (anonymous@undisclosed.example.com) — 2025-04-03T13:08:43+00:00

2009/08/14 10:58		current
Line 106:		Line 106:

	When the deploy.php script has finished, the servers are ready for installing the web applications (currently only phpBB).		When the deploy.php script has finished, the servers are ready for installing the web applications (currently only phpBB).
		+
		+	==Available files==
		+	* config.php
		+	Configuration before the deployment of the virtual machines
		+	* deploy.php START-IP
		+	Deployment script that deploys the three virtual machines to START-IP, START-IP + 1 and START-IP + 2.
		+	* functions.php
		+	Functions used for the deployment and upload/execution of commands.
		+	* installers/
		+	This is were the applications are stored
		+	* machines/
		+	This is were machine-specific files are stored, such as configuration-files and such.
		+	* roles/
		+	Here are the role-files places (files that choose which packages that are installed after the deployment)
		+	* setup.php
		+	This is a file that's included when all the servers has booted up in the deployment script and this performs configurations and additional setups.
		+	* shutdown.php
		+	This shutdowns (destroys) the virtual machines and removes the created files (ips.txt which contains the IP-adresses of the VM's) and the known_hosts file that is created when ssh and scp commands are executed.

	===phpBB3 benchmark===		===phpBB3 benchmark===

wheretohelp

Anonymous (anonymous@undisclosed.example.com) — 2025-04-03T13:08:43+00:00

2010/01/08 21:11		current
Line 1:		Line 1:
	===== Source Development =====		===== Source Development =====

-	The source code behind PHP is managed through the versioning system CVS. There are three active branches:	+	The source code behind PHP is managed through the versioning system SVN. There are three active branches:
-	* PHP 5.2 (Stable) is branched as PHP_5_2	+	* PHP 5.2 (Stable) is branched as [[http://svn.php.net/viewvc/php/php-src/branches/PHP_5_2/\|PHP_5_2]]
-	* PHP 5.3 (Development) is branched as PHP_5_3	+	* PHP 5.3 (Stable) is branched as [[http://svn.php.net/viewvc/php/php-src/branches/PHP_5_3/\|PHP_5_3]]
-	* PHP 6.0 (Alpha) is HEAD, so named php-src	+	* PHP 6.0 (Alpha) is [[http://svn.php.net/viewvc/php/php-src/trunk/\|trunk]]

-	In CVS, when checking out these modules it will also automagically include the TSRM, Zend and ZendEngine2 modules.	+	In SVN, when checking out these modules it will also automagically include the TSRM, Zend and ZendEngine2 modules.

	==== Getting the source code ====		==== Getting the source code ====
-	There are two main methods for getting the latest PHP source files, either directly from CVS or by downloading a Snapshot	+	There are two main methods for getting the latest PHP source files, either directly from SVN or by downloading a Snapshot

-	=== CVS ===	+	=== SVN ===
	This is where developers actively add/modify code. A few differences from snaps:		This is where developers actively add/modify code. A few differences from snaps:
-	* You can write patches or commit to CVS	+	* You can write patches or commit to SVN
	* You can test the build tools via buildconf		* You can test the build tools via buildconf
	* Should specify the branch when checking out		* Should specify the branch when checking out

	=== Snapshots ===		=== Snapshots ===
-	Each branch is built around four times a day, and the snapshots system runs a few scripts in order to lesson the burden of required tools for building. A few differences from CVS:	+	Each branch is built around four times a day, and the snapshots system runs a few scripts in order to lesson the burden of required tools for building. A few differences from SVN:
	* Snaps do not require all build tools like buildconf and flex		* Snaps do not require all build tools like buildconf and flex
	* It's easier to deal with		* It's easier to deal with
Line 38:		Line 38:
	* Internals docs		* Internals docs
	* Example extension		* Example extension
-	* All PECL extensions (CVS)	+	* All PECL extensions (SVN)

	=== Writing an extension ===		=== Writing an extension ===

pecldocs

Anonymous (anonymous@undisclosed.example.com) — 2025-04-03T13:08:43+00:00

2009/03/24 17:14		current
Line 17:		Line 17:
	</code>		</code>

-	This will create a directory named 'tmp' for the extension named 'extname' which will be full of documentation skeletons. Reflection is used to make guesses about the extension, like for classes, methods, functions, constants, parameters, version information, etc. but this information will not be fully correct. Please go through and edit each XML file by updating this information and adding documentation.	+	This will create a directory named 'tmp' that will contain documentation skeletons for the 'pecl' extension named 'extname'. Reflection is used to make guesses about the extension, like for classes, methods, functions, constants, parameters, version information, etc. but this information will not be fully correct. Please go through and edit each XML file by updating this information and adding documentation.

	* Read the Validating Changes section of the [[doc:scratchpad:howto\|PHP Documentation HOWTO]].		* Read the Validating Changes section of the [[doc:scratchpad:howto\|PHP Documentation HOWTO]].

namespacefaq

Anonymous (anonymous@undisclosed.example.com) — 2025-04-03T13:08:43+00:00

2008/10/28 11:51		current
Line 9:		Line 9:

	Q: Would removing constants/functions from namespaces make it possible to stick with "::" for namespaces?		Q: Would removing constants/functions from namespaces make it possible to stick with "::" for namespaces?
		+
		+	A: Yes, but at a cost. Functions and constants within namespaced files would throw a fatal error. [Reference needed]

	Q: Was the "::" separator was dropped because of limitations on the Zend Engine?		Q: Was the "::" separator was dropped because of limitations on the Zend Engine?

	Q: Was the fact that the "\" character is harder to type on various international keyboards considered and if so why was this character still chosen?		Q: Was the fact that the "\" character is harder to type on various international keyboards considered and if so why was this character still chosen?
		+
		+	A: Yes, it was considered. However the fact that "\" is already used in PHP means that nobody has a keyboard that actually lacks that character. There are also workarounds for those facing difficulties. [References needed]

	Q: Why was character combination XYZ (":::", "@" etc.) not chosen?		Q: Why was character combination XYZ (":::", "@" etc.) not chosen?
		+
		+	A: There have been long and intensive public discussions over the choice of namespace separator in the past, and everyone at the internals meeting was familiar with the arguments against a wide range of potential characters. The possibilities were therefore very limited, as documented on the wiki page about this decision. [Link to Lukas' entry]

	Q: Why was "\" chosen given that it makes it impossible to write something like "spl_autoload_register(array("myNamespace\theLoader", "load"));" because the \t would be interpreted as a tab?		Q: Why was "\" chosen given that it makes it impossible to write something like "spl_autoload_register(array("myNamespace\theLoader", "load"));" because the \t would be interpreted as a tab?
		+
		+	A: It is already impossible to write Windows paths in PHP in the same way, ergo at least half the PHP community is already familiar with the idea that they need to either use single quotation marks or escape the backslash ("\\").

	Q: Why do the PHP internals developer think that "\" is not prone to cause issues when typos are made?		Q: Why do the PHP internals developer think that "\" is not prone to cause issues when typos are made?
Line 22:		Line 30:
	Q: Don't the PHP internals developer think that the fact that "\" is widely used as the escape character will be cause for confusion?		Q: Don't the PHP internals developer think that the fact that "\" is widely used as the escape character will be cause for confusion?

-	Q: C++ uses "::" for namespaces, why did the PHP internals developer feel they needed to solve the ambiguity issues rather than leaving it to each developer to prevent ambiguity between namespace names and other identifiers?	+	A: No, because the usage context is completely different.
		+
		+	Q: C++ uses "::" for namespaces, why did the PHP internals developers feel they needed to solve the ambiguity issues rather than leaving it to each developer to prevent ambiguity between namespace names and other identifiers?
		+
		+	A: Ambiguity is an edge case, meaning that developers wouldn't necessarily be aware of the potential for it through their own past experience, and debugging would be extremely difficult. Further, there was no way to provide a PHP error message on ambiguity without impacting performance in all cases. [Reference needed]

	Q: Why wasn't the proposal chosen to just require "use namespace" and "use class" chosen?		Q: Why wasn't the proposal chosen to just require "use namespace" and "use class" chosen?

	Q: Do I have to prefix all my internal function names with \ now?		Q: Do I have to prefix all my internal function names with \ now?

faq

Anonymous (anonymous@undisclosed.example.com) — 2025-04-03T13:08:43+00:00

2026/09/01 06:49	current
Line 1:	Line 1:
	+	==== So, How exactly do I get the source files for the PHP Manual? ====
	+	Simple. The PHP Project uses CVS to manage its sources, so to retrieve the sources for the PHP Manual you will checkout (download) these sources from CVS. An anonymous CVS user named //cvsread// exists (password: //phpfi//) that anybody in the world may use to make checkouts. For example:
	+
	+	<code>
	+	$ cvs -d :pserver:cvsread@cvs.php.net:/repository login
	+	$ cvs -d :pserver:cvsread@cvs.php.net:/repository checkout phpdoc
	+	</code>
	+
	+	The above assumes you have CVS installed. Odds are if you're using Linux or Mac that this is already installed, but Windows users aren't so lucky (or unlucky, depending on your feelings towards CVS!) The simplest method for Windows users is TortoiseCVS, see the FAQ for that.
	+
	+	There will now exist a directory named //phpdoc// that houses all sources files for the PHP Manual.
	+
	+	==== I use Windows, and heard something about TortoirseCVS... should I use it? ====
	+	Sure, it's simple and offers a friendly GUI so if you're into that then go for it! And besides, it also installs the cvs command so it may be used in your Terminal too. The steps include:
	+
	+	* Install [[http://www.tortoisecvs.org/\|TortoirseCVS]]
	+	* Open a new explorer window and go to the folder you wish to do a checkout in (store CVS files)
	+	* Right click anywhere in the blank area to spawn the context menu, select "CVS Checkout"
	+	* A new window will popup and ask for details about the checkout; these values will be remembered so will be entered just once
	+	* Enter the following:
	+	* CVSROOT: ":pserver:cvsread@cvs.php.net:/repository"
	+	* Module field: "phpdoc"
	+	* Press OK to begin the checkout. If you're prompted to enter a password while checking out, then type in "phpfi" and OK
	+	* When the checkout is complete, then it should have created a directory called "phpdoc" where the english php documentation source tree will be
	+
	+	==== I was told to create a patch, how do I do that? ====
	+	== New Files ==
	+	== Current Files ==
	+
	+	==== How do I know if my changes are good and valid? ====
	+	* Whitespace
	+	* Read diff
	+	* php configure.php
	+	* Describe when editing manual.xml.in is needed
	+	* PhD
	+
	+	==== Is there an online editor? ====
	+	* Yes and No

checkout

Anonymous (anonymous@undisclosed.example.com) — 2025-04-03T13:08:43+00:00

2010/01/08 21:11		current
Line 1:		Line 1:
-	===== Checking out the PHP Manual sources from SVN =====	+	===== Checking out the PHP Manual sources from SVN =====

	==== Introduction ====		==== Introduction ====
Line 22:		Line 22:
	Several svn:externals already exist within phpdoc/modules and may be used. They are setup as doc-{lang} where {lang} is the language code for the desired language, and doc-all exists to include every language.		Several svn:externals already exist within phpdoc/modules and may be used. They are setup as doc-{lang} where {lang} is the language code for the desired language, and doc-all exists to include every language.

-	svn co http://svn.php.net/repository/phpdoc/modules/doc-en phpdoc	+	svn co https://svn.php.net/repository/phpdoc/modules/doc-en phpdoc

	So, that checks out via the svn:externals to a new local directory named phpdoc.		So, that checks out via the svn:externals to a new local directory named phpdoc.
Line 30:		Line 30:
	Sparse checkouts are another option.		Sparse checkouts are another option.

-	svn co http://svn.php.net/repository --depth empty phpdoc	+	svn co https://svn.php.net/repository --depth empty phpdoc
-	svn co http://svn.php.net/repository/phpdoc/en/trunk --depth infinity phpdoc/en	+	svn co https://svn.php.net/repository/phpdoc/en/trunk --depth infinity phpdoc/en
-	svn co http://svn.php.net/repository/phpdoc/doc-base/trunk --depth infinity phpdoc/doc-base	+	svn co https://svn.php.net/repository/phpdoc/doc-base/trunk --depth infinity phpdoc/doc-base

	==== Conclusion ====		==== Conclusion ====

53

Anonymous (anonymous@undisclosed.example.com) — 2025-04-03T13:08:43+00:00

2009/06/26 02:29		current
Line 1:		Line 1:
	====== PHP 5.3 upgrading notes ======		====== PHP 5.3 upgrading notes ======
	* This document has been removed in favor of [[http://cvs.php.net/viewvc.cgi/php-src/UPGRADING?view=markup&pathrev=PHP_5_3\|UPGRADING]] and will eventually live in the PHP Manual (see below)		* This document has been removed in favor of [[http://cvs.php.net/viewvc.cgi/php-src/UPGRADING?view=markup&pathrev=PHP_5_3\|UPGRADING]] and will eventually live in the PHP Manual (see below)
-	* The 5.3.0 upgrade guide can be seen here: [[http://php.net/migration53]]	+	* The 5.3.0 upgrade guide can be seen here: [[http://docs.php.net/migration53]]
-	* The 5.2.0 upgrade guide can be seen here: [[http://php.net/migration52]]	+	* The 5.2.0 upgrade guide can be seen here: [[http://docs.php.net/migration52]]
-	* The 5.1.0 upgrade guide can be seen here: [[http://php.net/migration51]]	+	* The 5.1.0 upgrade guide can be seen here: [[http://docs.php.net/migration51]]

upgrade

Anonymous (anonymous@undisclosed.example.com) — 2025-04-03T13:08:43+00:00

2008/05/14 17:22		current
Line 1:		Line 1:
	===== Upgrade and Migration information =====		===== Upgrade and Migration information =====
-	Information found here will one day live within the migration section of the PHP Manual. See the manual pages for [[http://php.net/migration51\|5.2]] and [[http://php.net/migration52\|5.2]] for example manual pages.	+	Information found here will one day live within the migration section of the PHP Manual. See the manual pages for [[http://php.net/migration51\|5.1]] and [[http://php.net/migration52\|5.2]] for example manual pages.

	* [[doc:scratchpad:upgrade:53\|5.3.0]]		* [[doc:scratchpad:upgrade:53\|5.3.0]]

howto

Anonymous (anonymous@undisclosed.example.com) — 2025-04-03T13:08:43+00:00

2011/04/06 10:59		current
Line 1:		Line 1:
-	This page has been removed, in favor of: [[doc/howto]]	+	This page has been removed, in favor of [[http://doc.php.net/tutorial/\|new guide]]