Hi Ben
On Tue, Jun 27, 2023 at 9:54 PM Ben Ramsey wrote:
>
> > On Jun 27, 2023, at 04:01, Ilija Tovilo wrote:
> >
> > Hi Ben, Hi Rowan
> >
> > On Mon, Jun 26, 2023 at 8:55 PM Ben Ramsey wrote:
> >>
> >>> On Jun 20, 2023, at 06:06, Rowan Tommins wrote:
> >>>
> >>> On Tue, 20 Jun 2023 at 10:25,
Hi Andreas,
śr., 28 cze 2023 o 07:55 Andreas Heigl napisał(a):
> ...
> While I like not adding more Superglobals, it seems like we are adding
> more and more functions to retrieve the different parts of a
> Request-Object...
>
> So when we are at it: Why don't we introduce exactly that? A
> Requ
Hey All
On 28.06.23 02:45, Larry Garfield wrote:
On Tue, Jun 27, 2023, at 3:26 PM, Stephen Reay wrote:
On 28 Jun 2023, at 02:53, Ben Ramsey wrote:
On Jun 27, 2023, at 04:01, Ilija Tovilo wrote:
Hi Ben, Hi Rowan
On Mon, Jun 26, 2023 at 8:55 PM Ben Ramsey wrote:
On Jun 20, 2023, at 06:0
On Tue, Jun 27, 2023, at 3:26 PM, Stephen Reay wrote:
>> On 28 Jun 2023, at 02:53, Ben Ramsey wrote:
>>
>>> On Jun 27, 2023, at 04:01, Ilija Tovilo wrote:
>>>
>>> Hi Ben, Hi Rowan
>>>
>>> On Mon, Jun 26, 2023 at 8:55 PM Ben Ramsey wrote:
> On Jun 20, 2023, at 06:06, Rowan Tommins w
> On 28 Jun 2023, at 02:53, Ben Ramsey wrote:
>
>> On Jun 27, 2023, at 04:01, Ilija Tovilo wrote:
>>
>> Hi Ben, Hi Rowan
>>
>> On Mon, Jun 26, 2023 at 8:55 PM Ben Ramsey wrote:
>>>
On Jun 20, 2023, at 06:06, Rowan Tommins wrote:
On Tue, 20 Jun 2023 at 10:25, Ilija Tovilo
> On Jun 27, 2023, at 04:01, Ilija Tovilo wrote:
>
> Hi Ben, Hi Rowan
>
> On Mon, Jun 26, 2023 at 8:55 PM Ben Ramsey wrote:
>>
>>> On Jun 20, 2023, at 06:06, Rowan Tommins wrote:
>>>
>>> On Tue, 20 Jun 2023 at 10:25, Ilija Tovilo wrote:
>>>
Introduce a new function (currently named po
Hi Ben, Hi Rowan
On Mon, Jun 26, 2023 at 8:55 PM Ben Ramsey wrote:
>
> > On Jun 20, 2023, at 06:06, Rowan Tommins wrote:
> >
> > On Tue, 20 Jun 2023 at 10:25, Ilija Tovilo wrote:
> >
> >> Introduce a new function (currently named populate_post_data()) to
> >> read the input stream and populate
> On Jun 20, 2023, at 06:06, Rowan Tommins wrote:
>
> On Tue, 20 Jun 2023 at 10:25, Ilija Tovilo wrote:
>
>> Introduce a new function (currently named populate_post_data()) to
>> read the input stream and populate the $_POST and $_FILES
>> superglobals.
>>
>
>
> My initial instinct was to di
On Tue, 20 Jun 2023 at 10:25, Ilija Tovilo wrote:
> Introduce a new function (currently named populate_post_data()) to
> read the input stream and populate the $_POST and $_FILES
> superglobals.
>
My initial instinct was to discuss how this could be made more flexible in
terms of input and outp
how are errors handled, like if the format of php://input is
unrecognized, not valid multipart/form-data and not valid
application/x-www-form-urlencoded?
errors? exceptions? nothing?
On Tue, 20 Jun 2023 at 11:26, Ilija Tovilo wrote:
>
> Hi internals
>
> A while ago I encountered a limitation of h
On Wed, Jun 17, 2009 at 08:23, Bharat Nagwani wrote:
>
> In php code, I see constants like TSRMLS_CC but cant find the definitions of
> these
http://blog.libssh2.org/index.php?/archives/22-What-the-heck-is-TSRMLS_CC-anyway.html
-Hannes
--
PHP Internals - PHP Runtime Development Mailing List
To
Andrei Zmievski kirjoitti:
Jani Taskinen wrote:
What branch and what lines? I checked PHP_5_2 and as far as I can
tell, there is no such function that simply returns when passed
track_vars_array is NULL..
Maybe HEAD is different, but that branch doesn't even compile so I
don't really have ti
Jani Taskinen wrote:
What branch and what lines? I checked PHP_5_2 and as far as I can tell,
there is no such function that simply returns when passed
track_vars_array is NULL..
Maybe HEAD is different, but that branch doesn't even compile so I don't
really have time for it.. :)
I was talki
Andrei Zmievski kirjoitti:
Why do we have safe_php_register_variable() calls there with NULL for
track_vars_array? The underlying code simply returns if that parameter
is NULL. Is it an oversight or some legacy stuff?
What branch and what lines? I checked PHP_5_2 and as far as I can tell, ther
On Sep 10, 2007, at 01:31:54, BuildSmart wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Sep 10, 2007, at 01:01:19, Christian Stocker wrote:
On 10.9.2007 6:53 Uhr, BuildSmart wrote:
On Sep 10, 2007, at 24:41:47, Christian Stocker wrote:
On 10.9.2007 3:53 Uhr, BuildSmart wrot
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Sep 10, 2007, at 01:01:19, Christian Stocker wrote:
On 10.9.2007 6:53 Uhr, BuildSmart wrote:
On Sep 10, 2007, at 24:41:47, Christian Stocker wrote:
On 10.9.2007 3:53 Uhr, BuildSmart wrote:
I was asked to look into the pdoru patch and ext
On 10.9.2007 6:53 Uhr, BuildSmart wrote:
>
> On Sep 10, 2007, at 24:41:47, Christian Stocker wrote:
>
>
>
>> On 10.9.2007 3:53 Uhr, BuildSmart wrote:
>>> I was asked to look into the pdoru patch and extension by a client, this
>>> is where I noticed that a similar patch is already applied to
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Sep 10, 2007, at 24:41:47, Christian Stocker wrote:
On 10.9.2007 3:53 Uhr, BuildSmart wrote:
I was asked to look into the pdoru patch and extension by a
client, this
is where I noticed that a similar patch is already applied to the
rfc1867.
On 10.9.2007 3:53 Uhr, BuildSmart wrote:
> I was asked to look into the pdoru patch and extension by a client, this
> is where I noticed that a similar patch is already applied to the
> rfc1867.c file
> (http://cvs.php.net/viewvc.cgi/php-src/main/rfc1867.c?r1=1.173.2.1&r2=1.173.2.1.2.1&pathrev=PH
19 matches
Mail list logo
