Greg,
sorry, "behavior" was probably not the right word. In any case, they
are different, because the one approach allows users to declare just
one namespace, and the other one allows to declare any number of
namespaces. That's what I meant. There really is no need for
ambiguities like th
If by fun you mean "Fatal error: Namespace cannot be declared twice
(without brackets) or nested within brackets in ..."
Ah, I didn't read it good enough - was under impression mixing them was
allowed.
--
Stanislav Malyshev, Zend Software Architect
[EMAIL PROTECTED] http://www.zend.com/
David Zülke wrote:
> I think there should be just one way to designate a namespace, not two
> different ones with different behaviors.
Hi David,
First, the behaviors are not different, just the syntax. Of course you
can have more than one namespace per file with brackets, but the stuff
within th
I think there should be just one way to designate a namespace, not
two different ones with different behaviors.
David
Am 21.08.2007 um 21:09 schrieb Gregory Beaver:
Stanislav Malyshev wrote:
What happens if you mix them?
That's not the fun yet. This is:
If by fun you mean "Fatal er
Stanislav Malyshev wrote:
>> What happens if you mix them?
>> >
>> namespace foo {
>> class Bar {
>> ...
>> }
>> }
>> ?>
>
> That's not the fun yet. This is:
>
> namespace baz;
>
> namespace foo { ...whatever... }
>
> class bar {}
>
> ?>
If by fun you mean "Fatal error: Namespace ca
