Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:98866
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.214.47 as permitted sender)
To: Sara Golemon <pollita@php.net>, PHP internals <internals@lists.php.net>
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>
Cc: Colin O'Dell <colinodell@gmail.com>
Message-ID: <5280684d-193b-dda8-efc6-903422522d7a@gmail.com>
Date: Mon, 24 Apr 2017 16:09:26 -0700
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:45.0)
 Gecko/20100101 Thunderbird/45.8.0
MIME-Version: 1.0
In-Reply-To: <CAESVnVrqD6HRij1zOd6Q5mmpE867=+r=XmFpL_z=V2aGvGeLnw@mail.gmail.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] [RFC] Enable strict_types checking for curl_setopt()
From: smalyshev@gmail.com (Stanislav Malyshev)

Hi!

> I disagree. From the user's perspective it is argument typing.  The

Not really. Argument typing is when arguments have types. curl_setopt
arguments do not have known types, they have business logic inside that
says if argument X is equal to this, then argument Y must be of that
type. It's very different from what strict_types does.

> internal implementation detail of that argument type being dependent
> on another arg's value is just a detail.

It's not "just a detail", it's the whole point of it. The value argument
does not have a know type, it is typed only when you know the exact
value of another argument (and sometimes not even then - e.g.
CURLOPT_POSTFIELDS accepts both strings and arrays). We don't have "type
that is defined by another type" in the type system, it's clearly
business logic. Which I have no problem with, but it shouldn't be part
of type system then.
-- 
Stas Malyshev
smalyshev@gmail.com