Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:109733
User-Agent: Cyrus-JMAP/3.1.7-1152-g08c8976-fmstable-20200420v1
Mime-Version: 1.0
Message-ID: <13736dc2-22b3-41ca-a70a-8374e26d394d@www.fastmail.com>
In-Reply-To: 
 <CAEPJdun_s9x6hxW7deiamJVae9OohZjzRDPr=2NcPMsGzu6mKw@mail.gmail.com>
References: 
 <CA+kxMuQ4ZrNEC76Mi7SxqijmwzxRrHD1ATgVrPkbZicUx7=YcQ@mail.gmail.com>
 <bbab0dfc-969c-451c-836b-77a17f176be6@www.fastmail.com>
 <CAESVnVooQoT3QzA+Xa-Tif7icw466pwmfx0tET98tnT4y2S05w@mail.gmail.com>
 <c1cdc94e-40f7-480d-80db-bbb08374a993@www.fastmail.com>
 <CAEPJdun_s9x6hxW7deiamJVae9OohZjzRDPr=2NcPMsGzu6mKw@mail.gmail.com>
Date: Mon, 20 Apr 2020 19:34:19 -0500
To: "php internals" <internals@lists.php.net>
Content-Type: text/plain
Subject: Re: [PHP-DEV] [RFC] Mixed type
From: larry@garfieldtech.com ("Larry Garfield")

On Mon, Apr 20, 2020, at 10:45 AM, Benjamin Eberlei wrote:

> > Sure, but how often is that an actual description of what the code
> > accepts?  I... cannot actually envision what code would actually accept
> > that mess. :-)
> >
> 
> I can think of quite a few:
> 
> - var_dump, print_r, more generally debugging/logging functions and
> wrappers thereof
> - json_encode, serialize, and more generally serialization and encoding
> functions, as return value as well for the inverse operations
> - database/nosql related functions (bindParam, bindValue) and as return
> value from generic functions like fetch()
> - Xpath::evaluate
> - ldap query functions
> 
> And wrappers of these extensions could benefit from passing on the mixed
> type explicitly.

Valid examples.  It would be helpful to add those to the RFC for clarity.

--Larry Garfield