Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:39850
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 74.125.44.30 as permitted sender)
DomainKey-Status: bad
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=message-id:date:from:sender:to:subject:cc:in-reply-to:mime-version
         :content-type:content-transfer-encoding:content-disposition
         :references:x-google-sender-auth;
        b=jl4y6MSyisuD2rsp1/eJ07PRakzsAw1DoRajqVKGOipb7Jl9mSQvq3ep4mK8AVucBx
         JS08SiBCl19j1vRKZ91Khw60qqvYQdbfgWGt6OVMoJ8EQdYkdh2gf3Ju8GEGykEUk5uR
         hMHX8hoLHrm0gviDUP+oWH6h1TotHEJfx/I8o=
Message-ID: <e666c3890808111702m5e95e83kc3b15afbf4cef99d@mail.gmail.com>
Date: Tue, 12 Aug 2008 02:02:53 +0200
Sender: ekneuss@gmail.com
To: "Stanislav Malyshev" <stas@zend.com>
Cc: hannes.magnusson@gmail.com, "Lukas Kahwe Smith" <mls@pooteeweet.org>, 
	"Marcus Boerger" <helly@php.net>, internals@lists.php.net
In-Reply-To: <48A0C415.9090104@zend.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <909776579.20080803142659@marcus-boerger.de>
	 <840985F2-A701-4BE4-91F6-F6B39048CF9B@pooteeweet.org>
	 <48A09FF4.1030101@zend.com>
	 <7f3ed2c30808111411t51553771j389f05c3436bc625@mail.gmail.com>
	 <48A0C415.9090104@zend.com>
Subject: Re: [PHP-DEV] Inconsistencies in 5.3
From: colder@php.net ("Etienne Kneuss")

Hello,

On Tue, Aug 12, 2008 at 12:58 AM, Stanislav Malyshev <stas@zend.com> wrote:
> Hi!
>
>> So why the $%#$%& can't we use "package" if the implementation has
>> nothing incommon with namespaces in c++ (your example, not mine)?
>
> We could use "package" or we could use "hexaflexagon" or we could use
> "triskaidekaphobia" or any other word. But if we have namespace
> implementation in PHP, why don't we call it "namespace"? Because it is
> "inconsistent" with C++? To hell with C++ then, nobody said PHP is C++.
>
>> Well. I do want that indentation if I ever will be dumb enough to have
>> multiple namespace in the same file..
>
> Indentation happens when you do () even once. {} implies that everything
> inside it is on next level of hierarchy and thus should be indented.
> Of course, it's "inconsistent" with Python, so maybe we should drop braces
> altogether...

I fail to see why { } meaning a different level of hierarchy is a
problem here, that's exactly what it's supposed to mean: "code in that
block is affected by that namespace."

We don't expect if's to work until the next if(), do we? Even though
ifs are not "entities like classes or functions".

Additionally, I see the packaging argument being raised to advocate
the use of multiple namespaces per file. However, with that syntax,
you can't package namespaced and non namespaced code in the same file
anyway, that sounds to me like a burden and actually a point against
the current syntax.

>
>> Its not about consistency for me. Its about that little gut feeling you
>> have.
>
> Well, of course I can not address little gut feeling with any logical
> argument. But to hell with logic and reasoning, let the little gut feeling
> rule.
> --
> Stanislav Malyshev, Zend Software Architect
> stas@zend.com   http://www.zend.com/
> (408)253-8829   MSN: stas@zend.com
>
> --
> PHP Internals - PHP Runtime Development Mailing List
> To unsubscribe, visit: http://www.php.net/unsub.php
>
>
>

Regards,

-- 
Etienne Kneuss
http://www.colder.ch

Men never do evil so completely and cheerfully as
when they do it from a religious conviction.
-- Pascal