Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:4360
Return-Path: <pollita@php.net>
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Delivered-To: mailing list internals@lists.php.net
Received: (qmail 8964 invoked by uid 1010); 2 Sep 2003 21:23:06 -0000
Delivered-To: ezmlm-scan-internals@lists.php.net
Delivered-To: ezmlm-internals@lists.php.net
Received: (qmail 8875 invoked by uid 1007); 2 Sep 2003 21:23:06 -0000
Message-ID: <20030902212305.8873.qmail@pb1.pair.com>
To: internals@lists.php.net
References: <20030828211521.99071.qmail@pb1.pair.com> <20030903061047dj4vK$@at.wakwak.com>
Date: Tue, 2 Sep 2003 14:22:51 -0700
Lines: 16
X-Newsreader: Microsoft Outlook Express 6.00.2800.1158
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
X-Posted-By: 169.229.139.92
Subject: Re: [PHP-DEV] Proposed Function: urlencode_array
From: pollita@php.net ("Sara Golemon")

Since Wez has been talking about an http_request() function (which inspired
the underlying php_url_encode_hash() function), using a name like
http_query_string() (or similar) might suffice for both naming conventions
and suitability.

-Sara

> I find this useful, but the name is a bit confusing because the function
> works differently than a combo of urlencode() / rawurlencode() and
> array_map(). One of my picks is build_query_string() (this doesn't conform
> to the naming convention though.)
>
> > proto urlencode_array(array formdata [, string numeric_prefix])
> >