Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:98486
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain brzuchalski.com designates 188.165.245.118 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <CAEDdnaV+pEyCn1nsMn8WAdNTX8+buynhCfP6e0h0JTcUhygBzQ@mail.gmail.com>
References: <CAEDdnaXrRnYQ24Dh7RdYmVdiYbBcXjnxo4_B0cNFe=FGewEbvQ@mail.gmail.com>
 <CAEDdnaV+pEyCn1nsMn8WAdNTX8+buynhCfP6e0h0JTcUhygBzQ@mail.gmail.com>
Date: Sun, 12 Mar 2017 06:24:05 +0100
Message-ID: <CABdc3Wr4-ikSZ_3gNSRzVNqbpZCO36_xtP6YxzfKjZX7s9S98Q@mail.gmail.com>
To: Michael Vostrikov <michael.vostrikov@gmail.com>
Cc: PHP Internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary=001a1148dd42ae9bb0054a81cd49
Subject: Re: [PHP-DEV] Type variants
From: michal@brzuchalski.com (=?UTF-8?Q?Micha=C5=82_Brzuchalski?=)

--001a1148dd42ae9bb0054a81cd49
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

2017-03-11 17:24 GMT+01:00 Michael Vostrikov <michael.vostrikov@gmail.com>:

> > 'Order does not match OrderForCheckout. Reason: ...'.
>
> Sorry, this is text for second example) I missed this moment. But I think
> the idea is clear.
>
>
> For manual call of __match() type casting can be used:
> $orderForCheckout =3D (OrderForCheckout)$order;
>
>
> Also this feature can be used for checking enum values or intervals.
>
> class Value
> {
>     public $value;
>
>     public function __construct($value)
>     {
>         $this->value =3D $value;
>     }
> }
>
> class State variant of Value
> {
>     const ACTIVE =3D 1;
>     const INACTIVE =3D 2;
>
>     public function __match()
>     {
>         return in_array($this->value, [self::ACTIVE, self::INACTIVE]);
>     }
> }
>
> function setState(State $s)
> {
>     ...
> }
>
> setState(new State(3));
>
> In constructions like "new State($value)" __match() can be called after
> __construct().
>
>
> If to add a possibility to use data types, class Value will not be needed=
:
>
> class State variant of integer
> {
>     ...
>     public function __match()
>     {
>         return in_array($this, [self::ACTIVE, self::INACTIVE]);
>     }
> }
>
> setState(3);
>

IMHO the real life implementations always differ, in another case, they
would be the same.
Example with Rectangle and Square IMO is an example of bad naming in this
case.
I rather want to call it Quadrangle and have one implementation or event do
the simplest inheritation.
But I may be wrong.

--=20
regards / pozdrawiam,
--
Micha=C5=82 Brzuchalski
about.me/brzuchal
brzuchalski.com

--001a1148dd42ae9bb0054a81cd49--