Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:10779
Return-Path: <sesser@php.net>
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Delivered-To: mailing list internals@lists.php.net
Received: (qmail 32363 invoked by uid 1010); 25 Jun 2004 18:38:05 -0000
Delivered-To: ezmlm-scan-internals@lists.php.net
Delivered-To: ezmlm-internals@lists.php.net
Received: (qmail 32338 invoked from network); 25 Jun 2004 18:38:05 -0000
Received: from unknown (HELO e-matters.de) (217.69.76.213)
  by pb1.pair.com with SMTP; 25 Jun 2004 18:38:05 -0000
Received: (qmail 15041 invoked by uid 0); 25 Jun 2004 18:36:48 -0000
Received: from p508d591d.dip.t-dialin.net (HELO ?192.168.1.77?) (80.141.89.29)
  by /var/run/qmail-smtp.pid with SMTP; 25 Jun 2004 18:36:48 -0000
Message-ID: <40DC70CB.5010400@php.net>
Date: Fri, 25 Jun 2004 20:36:59 +0200
User-Agent: Mozilla Thunderbird 0.7 (Windows/20040616)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To:  internals@lists.php.net
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Input Filters - Bugs? - PHP4 Port
From: sesser@php.net (Stefan Esser)

Hi,

am I correct in assuming that input_filters are allowed todo whatever 
they want with the value?

I am asking, because this is not properly documented and atleast the 
mbstring extension violates this.

First of all it feeds input_filter a value pointer that is NOT allocated 
with emalloc and secondly it free()s the wrong address in case the 
input_filter has erealloc()ated value (but most probably the erealloc() 
will already crash because the memory is allocated with malloc() instead 
of emalloc())

And the second question is: Is there any argument against backporting 
the input_filter functionality to PHP4? I do not know what the plans 
are, but I doubt PHP4 will die out with the release of PHP5 and so the 
question is if we partly backport new functionality for PHP4 from PHP5 
into PHP 4.4

Stefan