codingstandards

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

2009/07/25 10:55		current
Line 1:		Line 1:
	====== Coding Standards ======		====== Coding Standards ======
		+	* Use the [[http://pear.php.net/manual/en/standards.php\|PEAR coding standard]] (22/04/2009 - see php-qa list for concerns)
		+	* Deviation from the standard: Do not use _ prefix for private members. (Reason: too much re-work to existing code)
		+	* We prefix classnames with rt (Reason: avoid name conflicts with built-in PHP classes)
		+	* We do not follow the original PEAR class naming scheme (Reason: we use autoload and name prefixes, so we can keep classnames shorter than DIR_DIR_DIR_CLASS)
		+	* We will not include both File and Class doc blocks. (Reason: Only ever one class per file)
		+	* Don't use private, always use protected instead. (Requested by Greg)

notimplemented

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

2026/09/01 08:57	current
Line 1:	Line 1:
	+	====== Things which will not be re-implemented ======
	+
	+	===== GZIP_POST, DEFLATE_POST =====
	+	The way these are currently implemented the test has to look like this:
	+
	+	<code>
	+	--POST--
	+	Some posted content
	+
	+	--GZIP_POST--
	+	1
	+	--FILE--
	+	etc
	+	</code>
	+
	+	This isn't really necessary. In the new implementation the --GZIP_POST-- section will just contain the content to be posted and gzip'd. Same for DEFLATE_POST.
	+	This affects two tests:
	+
	+	* ext/soap/tests/server019.phpt
	+	* ext/soap/tests/server020.phpt
	+
	+