Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:48130
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.222.173 as permitted sender)
DomainKey-Status: bad
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:in-reply-to:references:from:date:message-id:subject:to
         :cc:content-type;
        b=oiHn5VRh3ftTtYTPEdkckHrs32v+1skoF6UVLhbrrAK4ukqqll4j/DT4MEQOgH1p6g
         G2cGiDPDodZV9qCjGLdKIf2LsFgCwm7H2G9u80g3Wcb0CDNqBshYnuqK6esuKo8OJLrH
         3rxO/QC5yNBs61OeRdrzdWoe245cxcW/ht3gU=
MIME-Version: 1.0
In-Reply-To: <1272493415.3021.75.camel@kheops>
References: <1272491141.3021.59.camel@kheops> <EFD8F7B1-2A55-4ADB-976E-51E254B9A97A@gmail.com> 
	<1272493415.3021.75.camel@kheops>
Date: Wed, 28 Apr 2010 15:29:24 -0700
Message-ID: <t2m76472c6f1004281529qc22de7cdp28b4350d069b04bf@mail.gmail.com>
To: sylvain@abstraction.fr
Cc: internals@lists.php.net
Content-Type: multipart/alternative; boundary=00504502c10dfb32b90485538bcb
Subject: Re: [PHP-DEV] backslash, really ... ?
From: chadfulton@gmail.com (Chad Fulton)

--00504502c10dfb32b90485538bcb
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

You can take a look at the RFP if you like. It discusses the pros and cons
of various possible separators, and why they chose the backslash.

http://wiki.php.net/rfc/namespaceseparator

<http://wiki.php.net/rfc/namespaceseparator>I've been using namespaces for =
a
few months now with the backslash syntax, and I have to say that it doesn't
effect the aesthetics or readability of my code. Give it some time, I
suspect you'll get used to it in no time.

On Wed, Apr 28, 2010 at 3:23 PM, Sylvain Rabot <sylvain@abstraction.fr>wrot=
e:

> On Wed, 2010-04-28 at 16:58 -0500, Matt Wilson wrote:
> > So, you decided to jump in to criticize a design decision that went in
> after several months of discussion, without any insight into why it was d=
one
> the way it was?
> >
>
> Not really criticizing, maybe a bit, but more expressing my
> disappointment regarding aesthetic loss that the choice made has lead
> to. It might not concern you but it does concern me and probably other
> people too.
>
> I admit I have no knowledge of what have been told during the months of
> discussion you are referring to. However, you seem to have this
> knowledge, so I would be grateful if you could tell me if the aesthetic
> of the backslash token has been discussed and even more if you can
> redirect me to a discussion thread.
>
> Regards.
>
> > On Apr 28, 2010, at 4:45 PM, Sylvain Rabot wrote:
> >
> > > Hi,
> > >
> > > The comment I'm about to make is behind the times, and, now, useless,=
 I
> > > know, but I can't hold me.
> > >
> > > You chose for the namespace feature, a great feature besides, the
> > > backslash ?? really ?? Come on guys, among all the possibilities, you
> > > have chosen, according to me, the most hideous character possible.
> > >
> > > Having Windows=A9=AE=99 path like strings in the middle of source cod=
e is not
> > > something that is going to make me use the feature.
> > >
> > > PHP syntax was simple, clean. To me, the backslash token ruins
> > > everything. Using it aside from escaping was something I have never
> > > considered, have you ? Do you like it ?
> > >
> > > The goal of backslash was maybe to highlight namespace in the source
> > > code, if it was, congrats, we only see that now.
> > > To my opinion it breaks all esthetic's balance of a source code.
> > >
> > > No need to respond that I should have contribute to the choice, belie=
ve
> > > me, if I could have, I would have.
> > >
> > > This was just the comment of a simple guy which is very concerned abo=
ut
> > > source code esthetic's and believes that a neat, well balanced code i=
s
> > > more likely to be well maintained that any other one.
> > >
> > > Best regards.
> > >
> > > --
> > > Sylvain Rabot <sylvain@abstraction.fr>
> >
> >
>
>
> --
> Sylvain Rabot <sylvain@abstraction.fr>
>

--00504502c10dfb32b90485538bcb--