Snapshot 5.3.0alpha3-dev acts like manual, I think the manual is correct.
BTW - this is very useful feature. A "wrong-relative-resolving" rescuer ;)
DG.
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
On Tue, Dec 2, 2008 at 23:34, Stanislav Malyshev <[EMAIL PROTECTED]> wrote:
The warning is correct.
>>>
>>> It is not correct - the use statement has effect, as documented in manual
>>> http://php.net/manual/en/language.namespaces.importing.php.
>>
>> The manual is wrong. Importing global obje
The warning is correct.
It is not correct - the use statement has effect, as documented in
manual http://php.net/manual/en/language.namespaces.importing.php.
The manual is wrong. Importing global object is use \ArrayObject - note
the \.
From the look of it it seems like the page there has al
The warning is correct.
It is not correct - the use statement has effect, as documented in
manual http://php.net/manual/en/language.namespaces.importing.php.
The manual is wrong. Importing global object is use \ArrayObject - note
the \.
--
Stanislav Malyshev, Zend Software Architect
[EMAIL PR
Hi!
but it generates Warning: The use statement with non-compound name
'ArrayObject' has no effect.
The warning is correct.
It is not correct - the use statement has effect, as documented in
manual http://php.net/manual/en/language.namespaces.importing.php.
DG.
--
PHP Internals - PHP Runt
On 02.12.2008, at 22:25, David Grudl wrote:
2) Relative Resolving
I pointed out to inappropriate relative resolving earlier (http://news.php.net/php.internals/41837
). In the world of well-written namespaced frameworks the ratio of
usage of "more nested" classes vs. "less nested" is in larg
Hi!
but it generates Warning: The use statement with non-compound name
'ArrayObject' has no effect.
The warning is correct.
What about voting?
We already voted a lot, let's actually release something for a change.
--
Stanislav Malyshev, Zend Software Architect
[EMAIL PROTECTED] http://ww
I just read the new namespace documentation and I must say that the new
implementation is much more flexible.
Great work!
I had only two objections:
1) False warnings
As http://php.net/manual/en/language.namespaces.importing.php says, it
is possible to import non-compound name.
// import