Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:63156
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.160.42 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <5059FCCD.3090309@ajf.me>
References: <CAO1hux8mmUsy4badiNjxTGMubaduD1gkgbw4ZK1Me_MwGwLybA@mail.gmail.com>
	<CALtuQzC4e2Sn_BHinFAPdVrz8Oc_d6wCqTr=AscMChH29NSENw@mail.gmail.com>
	<CAO1hux9+4QK2sVX9+4110ksa9qDpUpfDhFJvyzkXcBHrFoFWvg@mail.gmail.com>
	<0960EAA5-17FF-4E0F-9DDE-BB93D13EA02B@gmail.com>
	<CAO1hux9t9refYHYnKhY0725MvRm88ab85Ng23LCvnjDJxqQA7g@mail.gmail.com>
	<CALwr1GnjjjMbK8-VkVO57meDAgDn8PSPoWdj2DjYMB7F01dP4Q@mail.gmail.com>
	<CAPwsocGs=5-JfpSSewDRaNC0KaoNF1okBD8-E27fx5U=9f6sgw@mail.gmail.com>
	<72B22976-6F00-4EF5-88B3-140576CFE4E7@gmail.com>
	<CAH8KiX+AmGxnZ_j0KD-1FZ0gLOuYScEx9YURBQWAep_b1T6vTw@mail.gmail.com>
	<FE6A0705-9D5C-4FE4-AB1E-2FC18EFE4557@strojny.net>
	<5059F033.80706@ajf.me>
	<CAH8KiXJqew3gcPPOQbATHTQnm1zE1G6GNetAGXh4Cni8i_M6Kw@mail.gmail.com>
	<CAKa35F6AQATnBUq1XAuTK9+8xe_iMG4e6Yu+txxLjQ91wfaUFQ@mail.gmail.com>
	<5059FCCD.3090309@ajf.me>
Date: Wed, 19 Sep 2012 10:19:11 -0700
Message-ID: <CAKa35F6UHrUY+NgmqYZSTpJr=3fkfasQ8OuWW=Nb4dg2q_fpLA@mail.gmail.com>
To: Andrew Faulds <ajf@ajf.me>
Cc: Michael Stowe <me@mikestowe.com>, Lars Strojny <lars@strojny.net>, Leigh <leight@gmail.com>, 
	"internals@lists.php.net" <internals@lists.php.net>
Content-Type: text/plain; charset=UTF-8
Subject: Re: [PHP-DEV] RFC: Implementing a core anti-XSS escaping class
From: mike503@gmail.com (Michael Shadle)

On Wed, Sep 19, 2012 at 10:11 AM, Andrew Faulds <ajf@ajf.me> wrote:

> Please explain in detail how object-oriented code obfuscates, complicates,
> murders baby kittens, etc.

Because a simple str_replace one line will become 6-10 lines of OO
code very easily?

Maybe you write "amazing" OO code, but the stuff I see is usually
needless waste or reinventing core functionality and not adding any
additional value.

>> Next you'll start saying "why can't I do $string = new String();
>> $string->input($input); $string->replace($output);" or something,
>> instead of str_replace.
>
> Actually, I have. As an advocate of APIs with consistent argument order that
> newbies like me can learn more easily, I *have*, in fact, proposed that.

Your argument regarding consistent argument order is noted and agreed.
The needle/haystack/etc has always been an annoyance. But that's about
it.