Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:58110
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.216.170 as permitted sender)
Received-SPF: pass (google.com: domain of samuel.deal@gmail.com designates 10.224.101.72 as permitted sender) client-ip=10.224.101.72;
MIME-Version: 1.0
In-Reply-To: <9570D903A3BECE4092E924C2985CE4854FC3C828@MBX201.domain.local>
References: <CAG=uTXFQUY=EDb=ut97nNSm+m8sMQNRK-9YPcfb2quaoS246-g@mail.gmail.com>
	<CAO8n+WJrqUguS4FSq==z9rF6iLoz3uXqSLBrrkY6yMBY9DrTWA@mail.gmail.com>
	<CALtuQzD6f_vcZiGi2HWdP8SSqf9744FucUC+4sX7PnGhOnh+rg@mail.gmail.com>
	<4F455C96.50706@gmail.com>
	<4F455E91.2060408@alliantinternet.com>
	<028001ccf1ab$0b200050$216000f0$@alliantinternet.com>
	<4F457517.7050901@alliantinternet.com>
	<028d01ccf230$91d79b00$b586d100$@alliantinternet.com>
	<CAAyV7nHA_DhyZUqU2=EYDSvCEYmc7MFejsG97dXCoTtaeMurMg@mail.gmail.com>
	<4F4686C6.2040207@sugarcrm.com>
	<CAKOpQSwtHvSoSVj8q4_QTte42D588OUBDBQ_a4YB8q=GquekBQ@mail.gmail.com>
	<fe9c203ff43ec075a6f1a405053889ec.squirrel@www.l-i-e.com>
	<CAKOpQSwqddd1YUeuTGOQWX+V9SA_is-2UE1TOXfqt1YQoz2upw@mail.gmail.com>
	<CAG=uTXGTCxaEEOdt7cz81DT7vOOvMm1P0jdrgMX0CpY4e86t+Q@mail.gmail.com>
	<CAKOpQSy7r063FuoXpAy_7nsaBpz08LrVnz0zpa6CDF7fF-Tu6g@mail.gmail.com>
	<4F496818.8000405@sugarcrm.com>
	<CAKOpQSyewRGH8nZhXAZf9+hh1pU1oNGfZCn5rbfPW8Ydy9aH9g@mail.gmail.com>
	<4F4982BF.8090102@sugarcrm.com>
	<CAKOpQSwo0xy4tyZQW6zZGeuZgqCEGEqUpbD=iAWfa4TkaeeqrQ@mail.gmail.com>
	<CAL0xaBFwbmamuNCuakxv9jf2LXQQ4ej4RvFRm_UBD460Sazprg@mail.gmail.com>
	<CAKOpQSyi2Cpr=rYaWkkJZtyjcDzLVqr5QNUzLza1RQ9q27fA+A@mail.gmail.com>
	<CAGsnKxa+qqJqy++4pCTrnU1nG_Nf59TyTCpvaQtZSNTu-Byr5w@mail.gmail.com>
	<CAL0xaBEWmYYH9D7BEpUVEbGgSoP5QPWir8Qo+S4hz+CR53jdxA@mail.gmail.com>
	<CAKOpQSxmqWUbU-6_aS825mMwpNztHjiQy8WrZ-tJ6jUyhHSYRg@mail.gmail.com>
	<A633CF2D7C7BED41B41F1E64F25507B8069DC46B65@MAILR001.mail.lan>
	<CAKOpQSwHoUmMagvw_k_kjMNENzu_jR_G3417VGQVCdsG4L7OSA@mail.gmail.com>
	<9570D903A3BECE4092E924C2985CE4854FC3C828@MBX201.domain.local>
Date: Mon, 27 Feb 2012 03:10:25 +0100
Message-ID: <CAG=uTXHr06oJ1QYG9HyzM0kj4PFz3RHez87YUKE8696wCyOeKA@mail.gmail.com>
To: Clint M Priest <cpriest@zerocue.com>
Cc: Kris Craig <kris.craig@gmail.com>, John Crenshaw <johncrenshaw@priacta.com>, 
	Arvids Godjuks <arvids.godjuks@gmail.com>, 
	"internals@lists.php.net" <internals@lists.php.net>
Content-Type: multipart/alternative; boundary=20cf30667c2f13ca8904b9e89d6e
Subject: Re: [PHP-DEV] [RFC] Enum proposal (yet another)
From: samuel.deal@gmail.com (Samuel Deal)

--20cf30667c2f13ca8904b9e89d6e
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

+1 as well,

I start a new thread for that.
This debate is major for PHP's futur.

I'm little frustrated about this thread,
I don't have any new argument for or against the enum proposal.



2012/2/27 Clint M Priest <cpriest@zerocue.com>

> +1 for that as well.
>
> -----Original Message-----
> From: Kris Craig [mailto:kris.craig@gmail.com]
> Sent: Sunday, February 26, 2012 7:48 PM
> To: John Crenshaw
> Cc: Arvids Godjuks; internals@lists.php.net
> Subject: Re: [PHP-DEV] [RFC] Enum proposal (yet another)
>
> Well said, John!  I think that's a terrific idea!
>
> --Kris
>
>
> On Sun, Feb 26, 2012 at 5:44 PM, John Crenshaw <johncrenshaw@priacta.com
> >wrote:
>
> > > From: Kris Craig [mailto:kris.craig@gmail.com]
> > >
> > > I actually agree as well.  Looking back in the thread, I think my
> > > overly broad use of the word "strict" might have led to some
> > > confusion over what I'm advocating.
> >
> > Honestly, this is the biggest problem that the typing debates have had.
> > Someone advocates "strict typing" when they really mean "weak typing"
> > (as opposed to the current "dynamic typing") but there's always a
> > group of people that assume they mean "strict strict strict typing
> > like the old C days". People then panic and get frustrated because the
> > plethora of problems with adding this level of restriction to PHP have
> > already been discussed extensively. Discussion then devolves into
> > denigration and then finally disintegrates completely.
> >
> > If we can agree on some basic terminology I think it would move things
> > forward considerably. I propose these terms:
> > - "Strict Typing" means the super strict old C style typing that has
> > been proven to be ridiculous in this environment because of the
> > obvious problems inherent in the fact that almost every input is a
> string.
> > - "Weak Typing" means types in the same sense that the PHP
> > documentation uses types (for example, the docs indicate
> > substr(string, integer), and substr(12345, "2") =3D=3D "345".)
> > - "No Scalar Typing" should be used to indicate the current system
> > (where there is no provision for hinting at scalar types.)
> >
> > In addition, if someone potentially new expresses support for "Strict
> > Typing", let's assume that they really mean weak typing unless proven
> > otherwise (this is by far the more likely intent.) Politely clarify
> > terminology so that everyone can be on the same page. If someone still
> > insists that they want "Strict Typing", point them to the prior
> > discussions on the topic which explain exactly what the problems with
> this are.
> >
> > It might be wise to maintain a wiki article to keep track of the 3
> > different levels of typing, as well as a summary of the typical
> > arguments pro and con for each of the 3. If people agree that this
> > would be helpful, I'm willing to dig through the archives and try to pu=
t
> this together.
> >
> > John Crenshaw
> > Priacta, Inc.
> >
>
> --
> PHP Internals - PHP Runtime Development Mailing List
> To unsubscribe, visit: http://www.php.net/unsub.php
>
>


--=20
Samuel DEAL
samuel.deal@gmail.com
T=C3=A9l : +36 (0) 6.01.29.75.85
Adresse : 44, rue Jean Jaur=C3=A8s
92170 Vanves

--20cf30667c2f13ca8904b9e89d6e--