Re: New function proposal urlappendvar()
| From: | James Devenish | Date: | Wed, 21 Jan 2004 13:19:47 +0000 |
| Subject: | Re: New function proposal urlappendvar() | ||
| References: | 1 2 3 4 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-7243@lists.php.net to get a copy of this message | ||
In message <400E821D.8000103@delfi.lt>
on Wed, Jan 21, 2004 at 02:43:57PM +0100, Petras Kudaras wrote:
> Shouldn't that go into separate module (available from PEAR) or something?
> Sticking as many things into the core as possible seems to be the reason
> a lot of people don't like PHP ;)
I don't know what your preferred style is, nor what the "best" API would
be, so I don't attempt to make direct stylistic recommendations.
However, personally, I don't see why most users would appreciate such
features being "hidden" in PEAR (no offence intended!) when other
frequently-used string-handling functions are part of the compiled-in
modules (e.g. parse_url, urlencode, addslashes, htmlentities,
mysql_escape_string, etc.). You may conceive of URLs as objects that
should have a class structure in PEAR, but I suspect that manipulating
query strings and anchors is a vital procedural task in a vast number of
PHP scripts.