Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:58096
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.220.170 as permitted sender)
Received-SPF: pass (google.com: domain of kris.craig@gmail.com designates 10.220.153.16 as permitted sender) client-ip=10.220.153.16;
MIME-Version: 1.0
In-Reply-To: <4F4AA569.10502@gmail.com>
References: <CAG=uTXFQUY=EDb=ut97nNSm+m8sMQNRK-9YPcfb2quaoS246-g@mail.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>
	<4F4AA569.10502@gmail.com>
Date: Sun, 26 Feb 2012 13:49:40 -0800
Message-ID: <CAKOpQSz5vCXDr0Ms8HSD=5BXwuUxpnauc8QKXGAKYhC6cnpEEg@mail.gmail.com>
To: =?ISO-8859-1?Q?=C1ngel_Gonz=E1lez?= <keisial@gmail.com>
Cc: Arvids Godjuks <arvids.godjuks@gmail.com>, internals@lists.php.net
Content-Type: multipart/alternative; boundary=f46d043bdfe48a665804b9e4f853
Subject: Re: [PHP-DEV] [RFC] Enum proposal (yet another)
From: kris.craig@gmail.com (Kris Craig)

--f46d043bdfe48a665804b9e4f853
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Bleh well that's just semantics.  Strict typing / type hinting is what I'm
talking about; not specifically advocating one or the other.

And yeah this started as an enum proposal, but it came back to this issue.
 I offered to move this to a separate topic but everyone seems content to
just keep talking about it here.  I honestly don't care either way.  So
long as this important discussion isn't just "tabled" yet again I'm good.

--Kris


2012/2/26 =C1ngel Gonz=E1lez <keisial@gmail.com>

> On 26/02/12 05:11, Arvids Godjuks wrote:
> > Kris Craig
> >
> > I usually just read the list, sometimes add if I have something to say
> and
> > I had voiced my opinion on typehinting before. And you know, just from
> the
> > stand of a userland developer who has 7-8 years of experience and
> devoting
> > myself to the excelence at PHP, i see this discussion about adding stri=
ct
> > typehinting to PHP as ridicilous. I cannot express my thrustration,
> because
> > i would probably be kicked out of the list permanently.
> > The problem is that those, who are actually advocating for this, come
> from
> > all sorts of languages (or have moved to them some time ago) and now wh=
at
> > to "make php better". Sorry folks, but I have picked up a script langua=
ge
> > not because it has strict type hinting, but actually because it does no=
t
> > have it. And because in web we are working with text. Almost any data w=
e
> > get is text and in critical places we just check that data we have is
> > actually a number and not a random string. Or is an object of certain
> type.
> > Or is an array. Or a valid string. And we let the PHP to handle routine
> > conversions. And it's good because there can be tons of them per single
> > script call. String to number and vice-verse conversions are all over t=
he
> > place in almost any script. They are so common, that if you would add
> > strict typehinting - you would probably need a type conversion on every
> > function/method call.
> I'm not so sure about that. In a well-written web application, you would
> typically convert them on the first layer, when receiving from the web.
> On next usages, your int variables are usually ints already.
>
> Anyway, you seem to think that people is advocating to add strict typing
> to the language, while I haven't seen that in this thread. Only to add ty=
pe
> hinting (and this all began with an enum proposal!), which could be eithe=
r
> strict or weak.
> Some people positioned against typehints, have been much more vocal
> against strict, of course, as that has much more ground.
>
>
> --
> PHP Internals - PHP Runtime Development Mailing List
> To unsubscribe, visit: http://www.php.net/unsub.php
>
>

--f46d043bdfe48a665804b9e4f853--