Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:96587
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain basereality.com from 74.125.82.51 cause and error)
Content-Type: text/plain;
	charset=us-ascii
Mime-Version: 1.0 (1.0)
In-Reply-To: <CAEUnE0cA4EdaYZwAkejVtuVX0e8W+PtojnY36_Wfo9OhgSAA0Q@mail.gmail.com>
Date: Mon, 24 Oct 2016 11:16:56 +0100
Cc: PHP Internals List <internals@lists.php.net>
Content-Transfer-Encoding: quoted-printable
Message-ID: <E7E7645A-799A-41DF-A035-E2B4B46BE857@basereality.com>
References: <CABdc3WpeqPVfz=RgViAg55pXT_XdgWWWBngTReed31Tt1rwk1g@mail.gmail.com> <CAEUnE0cA4EdaYZwAkejVtuVX0e8W+PtojnY36_Wfo9OhgSAA0Q@mail.gmail.com>
To: Michael Morris <tendoaki@gmail.com>
Subject: Re: [PHP-DEV] [RFC][DISCUSSION] Object type hint
From: danack@basereality.com (Dan Ackroyd)


> On 24 Oct 2016, at 07:45, Michael Morris <tendoaki@gmail.com> wrote:
>=20
> My principle worry with this RFC is it encourages an anti-pattern - not
> using interfaces and thereby not clearly labeling what objects can and
> cannot do.
>=20

You've stated that as fact without any supporting argument, as far as I can s=
ee.

Any piece of functionality can be abused and used for purposes other that th=
e use-cases which it was intended for.

But I don't see how this RFC 'encourages' what you consider to be a bad prac=
tice. Instead it provides a useful thing that could be misused by bad progra=
mmers.=20

We shouldn't be designing the language so that it can't be misused by bad pr=
ogrammers - instead we should be designing it so that competent programmers h=
ave the tools that they want.

And yes, not everyone will need/want this piece of functionality, but for th=
e people who do want it, saying that they can't have it because it might be m=
isused seems illogical to me.=20

cheers
Dan=