Bug #66862 [Opn->Csd]: (Sub-)Namespaces unexpected behaviour
Edit report at https://bugs.php.net/bug.php?id=66862&edit=1
ID: 66862
Updated by: nikic@php.net
Reported by: celestino dot diaz at gmx dot de
Summary: (Sub-)Namespaces unexpected behaviour
-Status: Open
+Status: Closed
Type: Bug
Package: Scripting Engine problem
Operating System: LINUX
PHP Version: 5.5.10
-Assigned To:
+Assigned To: nikic
Block user comment: N
Private report: N
Previous Comments:
------------------------------------------------------------------------
[2016-10-08 15:03:49] nikic@php.net
Automatic comment on behalf of nikic
Revision: http://git.php.net/?p=php-src.git;a=commit;h=2a75f5026a47099f585e29c5a9d8a2989dab42af
Log: Fix bug #66773, #66862
------------------------------------------------------------------------
[2016-06-24 19:17:17] cmb@php.net
Related To: Bug #70671
------------------------------------------------------------------------
[2014-06-04 11:19:42] ajrattink at correct dot net
A similar simpler case:
c.php: namespace B; use A\Item;
b.php: namespace B; class Item {};
main.php: require 'b.php'; require 'c.php'; FATAL error
main.php: require 'c.php'; require 'b.php'; No problem at all
Our system worked fine but unexpectedly started crashing because someone declared a new class that
suddenly caused a conflict in an included file elsewhere.
Namespaces were supposed to just fix that problem.
I would like that namespaces worked completely static and on a per unit level. The way it is
designed suggests that it should work that way...
------------------------------------------------------------------------
[2014-03-16 20:06:07] celestino dot diaz at gmx dot de
Missed subnamespace declaration in test script:
Sample\Subnamespace\classA.php:
<?php
namespace Sample\Subnamespace;
class classA {}
------------------------------------------------------------------------
[2014-03-09 18:10:52] celestino dot diaz at gmx dot de
changed PHP version
------------------------------------------------------------------------
The remainder of the comments for this report are too long. To view
the rest of the comments, please view the bug report online at
https://bugs.php.net/bug.php?id=66862
--
Edit this bug report at https://bugs.php.net/bug.php?id=66862&edit=1
Thread (5 messages)