Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:67956
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gdesolutions.com designates 216.32.181.186 as permitted sender)
Received-SPF: softfail (mail106-ch1: transitioning domain of gdesolutions.com does not designate 132.245.2.69 as permitted sender) client-ip=132.245.2.69; envelope-from=jbondc@gdesolutions.com; helo=BN1PRD0712HT003.namprd07.prod.outlook.com ;.outlook.com ;
To: Anthony Ferrara <ircmaxell@gmail.com>
CC: "internals@lists.php.net" <internals@lists.php.net>
Thread-Topic: [PHP-DEV] RFC: Protocol Type Hinting
Thread-Index: AQHOcfelI2P2jDEJxkGUTfP2up+NEJlJnMUA
Sender: Jonathan Bond-Caron <jbondc@gdesolutions.com>
Date: Thu, 27 Jun 2013 14:47:41 +0000
Message-ID: <6AA5D154FC52C047B1FF1CA3759A935B3CD88D29@BN1PRD0712MB650.namprd07.prod.outlook.com>
References: <CAAyV7nGo4+n_4Ad7oKyuvLWTtmnui7fn6s-noCwG2PtT5A70tQ@mail.gmail.com>
	<51C9FA9C.8050403@sugarcrm.com>
	<CAAyV7nHz0E2Tmin5_S4OVii=U1HhuKKL6y_KAa+j=X7DT9My6g@mail.gmail.com>
	<51CA1C93.6080500@sugarcrm.com>
 <CAAyV7nHo-ZLx2F=+6URctZXTqx8tLgR=xG7j0wJ3unmiCxGvXQ@mail.gmail.com>
In-Reply-To: <CAAyV7nHo-ZLx2F=+6URctZXTqx8tLgR=xG7j0wJ3unmiCxGvXQ@mail.gmail.com>
Accept-Language: en-CA, en-US
Content-Language: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: RE: [PHP-DEV] RFC: Protocol Type Hinting
From: jbondc@openmv.com ("jbondc@openmv.com")

>I agree the use-cases are slightly weak. This is a draft RFC. It's suppose=
d to help identify=20
> the areas where we can improve it. Help identify use-cases. Help dig it o=
ut.

I think Ralph has the right idea:
register_compatible_types($yourType, $myType);

A better name might be (only for interfaces):
register_instanceof($compatibleInterface, $interface);

e.g.
class ThirdParty {
  static foo(LoggerInterface $log) {}
}

class Bar implements My_Logging_Inferface {}

echo (Bar instanceof LoggerInterface); // false

register_instanceof('My_Logging_Inferface', 'LoggerInterface');

echo (Bar instanceof LoggerInterface); // true

ThirdParty::foo(new Bar); // no error since 'My_Logging_Interface' is compa=
tible with LoggerInterface

In summary, it would allow for user-land registration of compatible interfa=
ces to third party libraries.

There's definitely a couple of use cases where I would have liked to use so=
mething to this.

Advantages to wrapping the feature in a function:
- No extra syntax to support in core
- No 'new concept' for developers to learn=20
- It can be disabled (which OO purists might like)
disable_functions =3D register_instanceof