Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:98872
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.128.172 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <CAESVnVomUDBqUNv4mCM_d=d5DWiMvHGPjhp89zXDg8yvN4f1nw@mail.gmail.com>
References: <CAJaRsPsfWtKbke8VvM-na=vCm0E6T62gmamj2V8sJiHRFB7FLQ@mail.gmail.com>
 <a5230c9c-c699-322b-ba56-09e74049b41b@gmail.com> <82da5975-aaca-580c-50ae-0b034d14b124@fleshgrinder.com>
 <CAESVnVrqD6HRij1zOd6Q5mmpE867=+r=XmFpL_z=V2aGvGeLnw@mail.gmail.com>
 <5280684d-193b-dda8-efc6-903422522d7a@gmail.com> <CAESVnVomUDBqUNv4mCM_d=d5DWiMvHGPjhp89zXDg8yvN4f1nw@mail.gmail.com>
Date: Tue, 25 Apr 2017 06:00:23 +0200
Message-ID: <CABdc3Wrr96X_TZsPBwRpn7_7kKRfB4uEXKfMuriWAv9+AihSbQ@mail.gmail.com>
To: Sara Golemon <pollita@php.net>
Cc: "Colin O'Dell" <colinodell@gmail.com>, PHP Internals List <internals@lists.php.net>, 
	Stanislav Malyshev <smalyshev@gmail.com>
Content-Type: multipart/alternative; boundary=94eb2c0d9ff06c1a44054df5c302
Subject: Re: [PHP-DEV] [RFC] Enable strict_types checking for curl_setopt()
From: michal.brzuchalski@gmail.com (=?UTF-8?Q?Micha=C5=82_Brzuchalski?=)

--94eb2c0d9ff06c1a44054df5c302
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

25.04.2017 01:56 "Sara Golemon" <pollita@php.net> napisa=C5=82(a):
>
> On Mon, Apr 24, 2017 at 4:09 PM, Stanislav Malyshev <smalyshev@gmail.com>
wrote:
> > it's clearly
> > business logic. Which I have no problem with, but it shouldn't be part
> > of type system then.
> >
> We're certainly arguing semantics at this point.  Let's agree that
> type enforcement is a good thing (which you seemed to say in your
> first response) and move on to how that's implemented.

I agree with Stanislav. IMHO argument types are valueable when are
reflective by reflection and curl_setopt has no valuable info by reflection
and will never be. Curl implementation also uses resources cURL handle is
used. Maybe it's time to refactor and provide objects with option setters
with argument types?

>
> Why shouldn't we allow the same call-time decision making around
> strict/weak enforcement to apply to "business logic" type enforcement
> as it does to argument types?  Surely consistency is a good thing as
> well?
>
> -Sara
>
> --
> PHP Internals - PHP Runtime Development Mailing List
> To unsubscribe, visit: http://www.php.net/unsub.php
>

--94eb2c0d9ff06c1a44054df5c302--