Hi,
that wiki page is pretty much up to date. Also, if you have windows
specific questions, there is internals-...@lists.php.net .
Regards
Anatoliy
On Mon, 2012-12-24 at 11:01 -0800, j adams wrote:
> Hello all:
>
> I'm not sure if this is the right place to ask this question, but I'm
> wonder
On Mon, Dec 24, 2012 at 7:13 AM, Anthony Ferrara wrote:
> Sherif,
>
>
> You're right. It does break BC, but this was a bug fix.
>> https://bugs.php.net/bug.php?id=61038
>>
>> The behavior is incorrect in that regard.
>>
>
> However in this case that *bug* does have fairly significant BC
> implicat
On Mon, 24 Dec 2012 12:13:35 -, Anthony Ferrara
wrote:
You're right. It does break BC, but this was a bug fix.
https://bugs.php.net/bug.php?id=61038
The behavior is incorrect in that regard.
However in this case that *bug* does have fairly significant BC
implications.
In fact, how I
Hello all:
I'm not sure if this is the right place to ask this question, but I'm
wondering if there might be an update available for this wiki describing
how to compile on Windows:
https://wiki.php.net/internals/windows/stepbystepbuild
In particular, there are a couple of aspects to that wiki ent
Hi all,
I know this topic was opened a long time ago, but I would like to get
it resolved before 5.5 got released.
One solution proposed by Richard Lynch was to add a new
CURLOPT_FILEFIELDS that takes an array of the parameters that are
supposed to be files, so the ones that are expected to have
Hi all,
Stas opened a discussion almost a year ago about
https://bugs.php.net/bug.php?id=46439 (I let you read details in the
bug) and I would like to reopen the subject since there was no end to
this discussion and nothing was made to fix this issue.
One solution proposed by Richard Lynch was to
Hi:
On Sun, Dec 23, 2012 at 11:36:14PM -0500, Sherif Ramadan wrote:
> On Sun, Dec 23, 2012 at 11:24 PM, Igor Wiedler wrote:
>
> > In that case I was mistaken regarding the new "Z" char. But "a" has been
> > changed. It is noted in the UPGRADING file.
>
> You're right. It does break BC, but this
Sherif,
You're right. It does break BC, but this was a bug fix.
> https://bugs.php.net/bug.php?id=61038
>
> The behavior is incorrect in that regard.
>
However in this case that *bug* does have fairly significant BC
implications.
In fact, how I read the specification is that the original binary
Tjerk,
I've been hearing this argument from time to time and I don't understand
> it; aren't exceptions created with the sole purpose of (error) flow
> control?
>
> If so, then how can "exceptions for flow control" and "very bad idea" be
> mentioned in the same sentence unless there are particular
On Tue, 18 Dec 2012, Adam Harvey wrote:
> On 18 December 2012 04:52, Lars Strojny wrote:
> > I would go with DateTimeValue or DateTimeImmutable as well.
>
> +1. I'd prefer DateTimeImmutable personally because it describes what
> it is better than the other options.
That's what I have changed it
10 matches
Mail list logo
