there was a problem with bugs.php.net, so the captcha error was on our end.
thanks for the report
On Mon, Oct 3, 2011 at 10:01 AM, Olivier Favre wrote:
> I finally managed to submit the patch... I used iceweasel 6.0.2
> instead of Google Chrome 14.0.835.186... or maybe the captcha was just
> in a
I finally managed to submit the patch... I used iceweasel 6.0.2
instead of Google Chrome 14.0.835.186... or maybe the captcha was just
in a better mood!
The link to the bug report: https://bugs.php.net/bug.php?id=55835
Yours,
--
Olivier Favre
Software engineer
Yakaz
www.yakaz.com
2011/9/30 Oliv
I keep on having the following error:
ERROR:
⋅ Incorrect Captcha
while trying to file a bug on the following page:
https://bugs.php.net/report.php
(Debian sid, Google Chrome 14.0.835.186)
I tried flushing my cookies.
There are two opened bug reports about that:
- https://bugs.php.net/
Gustavo Lopes wrote:
const char * and char const * are the same (just like const int and
int const are the same); what's not the same is char *const.
Andrey Hristov wrote:
it's easy, whatever const is closer to is immutable
const char * is a pointer to a const char, because the const is close
On 09/29/2011 07:13 PM, Ángel González wrote:
On 29/09/11 17:42, Olivier Favre wrote:
I checked with a tiny test program, you're right about GCC complaining.
The right fix is to make the field const (I don't know about const
keyword).
G++ won't give warnings, no error would be triggered by a bro
On Thu, 29 Sep 2011 18:13:34 +0100, Ángel González
wrote:
On 29/09/11 17:42, Olivier Favre wrote:
I checked with a tiny test program, you're right about GCC complaining.
The right fix is to make the field const (I don't know about const
keyword).
G++ won't give warnings, no error would be
On 29/09/11 17:42, Olivier Favre wrote:
I checked with a tiny test program, you're right about GCC complaining.
The right fix is to make the field const (I don't know about const keyword).
G++ won't give warnings, no error would be triggered by a broken fix.
By the way, const char* and char cons
I checked with a tiny test program, you're right about GCC complaining.
The right fix is to make the field const (I don't know about const keyword).
G++ won't give warnings, no error would be triggered by a broken fix.
By the way, const char* and char const* are the same, you probably
meant char *
On 29/09/11 14:14, Olivier Favre wrote:
Hi everyone,
I've been developing a PHP extension for internal needs.
We're using C++, by using PHP_REQUIRE_CXX() in config.m4.
I'm using debian sid 64bits, with the package php5-dev-5.3.8-2
(against which the patch below has been created).
(...)
My poin
Hi everyone,
I've been developing a PHP extension for internal needs.
We're using C++, by using PHP_REQUIRE_CXX() in config.m4.
I'm using debian sid 64bits, with the package php5-dev-5.3.8-2
(against which the patch below has been created).
When declaring an INI entry, like this:
PHP_INI_BEGI
10 matches
Mail list logo
