Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:79105
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain devtemple.com from 50.116.27.81 cause and error)
To: <internals@lists.php.net>
Date: Sun, 23 Nov 2014 10:39:18 -0800
Message-ID: <012701d0074c$ccfe6f40$66fb4dc0$@devtemple.com>
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_0128_01D00709.BEDC19A0"
Content-Language: en-us
Thread-Index: AdAHR+2wpA17pH7uRJ+8sCnt0clojQ==
Subject: enhance fget to accept a callback
From: bill@devtemple.com ("Bill Salak")

------=_NextPart_000_0128_01D00709.BEDC19A0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit

Hi list,

 

I'm considering writing an RFC to add a 3rd parameter to fgets which accepts
a user defined function. If we had this today we wouldn't need fgetcsv with
the added benefit of fgetcsv style support for data packaging formats we
would otherwise create more 1 off functions for.  For example, if we decided
to support reading json from files in the same manner as our current fgetcsv
functionality today, we would create an fgetjson function. 

 

This change unifies the way in which we support native transliteration of
data packaging formats from files into php data structures through a single
interface. The other major design benefit, from my point of view, is the
unification of userland transliteration functions/libraries with the same
modality as our native support for these types of use cases. I believe this
will ultimately result in more intuitive userland code around this type of
functionality.

 

Before I go any further in formalizing my proposal, I'd like to get feedback
from list members.

 

Thanks for your time.

Bill Salak

 

 


------=_NextPart_000_0128_01D00709.BEDC19A0--