Differences

This shows you the differences between two versions of the page.

--- rfc:namespaceissues [2008/10/16 03:45] – add clarification about existing "use" statements cellog
+++ rfc:namespaceissues [2017/09/22 13:28] (current) – external edit 127.0.0.1
@@ Line 1: / Line 1: @@
 ====== Request for Comments: Namespace Issues and Greg's Solutions ======
-  * Version: 1.1
+  * Version: 1.1.1
   * Date: 2008-10-15
   * Author: Greg Beaver <cellog@php.net>
@@ Line 46: / Line 46: @@
 </code>
-==== Why Stas's proposed solution doesn't work ====
-[[rfc:namespaceref#namespaces_with_functionsconstants|Stas's proposed solution]] suggests:
-> New syntax for static access is introduced: using ''Name->Member'' is the same as ''Name::Member'', e.g.:
-<code>
-ClassName->Foo() - static method call
-ClassName->$Foo - static property access
-ClassName->Foo - class constant access
-</code>
-Although this would in theory solve the ambiguity, it does not solve the ambiguity for all existing code, which as we know uses this syntax:
-<code php>
-<?php
-ClassName::Foo();
-?>
-</code>
-In fact, this proposal would require every single reference to a static method or class constant to be rewritten as ClassName->Foo(), a major shift in the language.  Inertia will prevent PHP developers from doing this, just as it has for all other quick fixes introduced.  For example, many PHP projects circumvented the need to rewrite code that relied upon register_globals by simply importing $_GET and $_POST into the global space, introducing a whole new host of security issues that Stefan Esser and others have repeatedly ranted about with good reason.
-The only fixes that can solve the problem are fixes that do **not** force PHP developers to rewrite code.  Every proposal below would only require changes to as-yet-unwritten code.  Solution #3 would in fact not even require changes to code written based on PHP 5.3alpha2.  Solution #1 and #2 would require code based on PHP 5.3alpha2 namespaces to be modified, and Solution #4 may require re-factoring of code if namespaces and classes share the same name.
 ==== The solutions ====
@@ Line 210: / Line 188: @@
 This will be better for 99% of scripts, as evidenced by the ratio of internal vs. userspace classes (see http://marc.info/?l=php-internals&m=122127176407546&w=2 for detail)
+===== Why Stas's proposed solution doesn't work =====
+[[rfc:namespaceref#namespaces_with_functionsconstants|Stas's proposed solution]] suggests:
+> New syntax for static access is introduced: using ''Name->Member'' is the same as ''Name::Member'', e.g.:
+<code>
+ClassName->Foo() - static method call
+ClassName->$Foo - static property access
+ClassName->Foo - class constant access
+</code>
+Although this would in theory solve the ambiguity, it does not solve the ambiguity for all existing code, which as we know uses this syntax:
+<code php>
+<?php
+ClassName::Foo();
+?>
+</code>
+In fact, this proposal would require every single reference to a static method or class constant to be rewritten as ClassName->Foo(), a major shift in the language.  Inertia will prevent PHP developers from doing this, just as it has for all other quick fixes introduced.  For example, many PHP projects circumvented the need to rewrite code that relied upon register_globals by simply importing $_GET and $_POST into the global space, introducing a whole new host of security issues that Stefan Esser and others have repeatedly ranted about with good reason.
+The only fixes that can solve the problem are fixes that do **not** force PHP developers to rewrite code.  Every proposal below would only require changes to as-yet-unwritten code.  Solution #3 would in fact not even require changes to code written based on PHP 5.3alpha2.  Solution #1 and #2 would require code based on PHP 5.3alpha2 namespaces to be modified, and Solution #4 may require re-factoring of code if namespaces and classes share the same name.
 ===== Changelog =====
   * Version 1.1: add [[#why_stas_s_proposed_solution_doesn_t_work|new section]] to explain why ClassName->Blah fails to solve the problem
+  * Version 1.1.1: move Classname->Blah to bottom of proposal for reading flow

Differences

Page Tools