I've been working on making PHP build under more stringent error
checking, specifically -Wextra under GCC. This patch cleans up dozens
of struct initializations that are valid C, but could hide future
problems.
xoxo,
Andy
--
Andy Lester => [EMAIL PROTECTED] => www.petdance.com => AIM:petdance
I
On 25.11.2007 19:55, Rachmel, Nir (Nir) wrote:
> If it helps, I am attaching the relevant tsrm_ls (according to the
> globals_id in the relevant frame):
> syslog_started = 1,
> syslog_device = 0x5a5a5a5a ,
So it's somehow got freed.
Try setting breakpoint to zm_shutdown_syslog() function to
Ezra Nugroho wrote:
> Can I ask for the following support, at least to begin conversation
> about it if it hasn't been done before.
>
> Currently, the header() function still carries the following warning in
> its online documentation:
>
> "Remember that header() must be called before any actual
Php Developers,
Can I ask for the following support, at least to begin conversation
about it if it hasn't been done before.
Currently, the header() function still carries the following warning in
its online documentation:
"Remember that header() must be called before any actual output is sent,
>> - static always points to the original callee, w/o being "broken" by
>> parent::
>> - get_called_class() should _not_ behave like shown above. It really was
>> not B that got called, but it was A, trough parent::
>> - a new get_static_class() method should return "B".
>
> Ouch. So now not only w
Hi!
Of course, we can't make parent:: reference the parent class of the called
one, as it would break BC.
As in:
class A { }
class B extends A { public static function test() { echo get_class(new
parent), '-', get_parent_class(); } }
class C extends B { }
C::test(); // A-A and not B-B
Maybe y
Am 26.11.2007 um 19:13 schrieb Stanislav Malyshev:
- static always points to the original callee, w/o being "broken"
by parent::
- get_called_class() should _not_ behave like shown above. It
really was not B that got called, but it was A, trough parent::
- a new get_static_class() method sho
- static always points to the original callee, w/o being "broken" by
parent::
- get_called_class() should _not_ behave like shown above. It really was
not B that got called, but it was A, trough parent::
- a new get_static_class() method should return "B".
Ouch. So now not only we have parent:
Hello Hans-Peter,
can you add tests so we get a better idea?
cvs add ; cvd di -N > patchfile.txt
marcus
Monday, November 26, 2007, 5:43:33 PM, you wrote:
> Index: ext/pdo/pdo_dbh.c
> ===
> RCS file: /repository/php-src/ext/pdo/p
Hi!
I "enhanced" my previous patch with the possibility of zero key rows...
HPO
Index: ext/pdo/pdo_dbh.c
===
RCS file: /repository/php-src/ext/pdo/pdo_dbh.c,v
retrieving revision 1.82.2.31.2.17.2.2
diff -u -r1.82.2.31.2.17.2.2 pdo_db
Am 26.11.2007 um 10:24 schrieb Alexey Zakhlestin:
On 11/26/07, Mike Lively <[EMAIL PROTECTED]> wrote:
class A {
public static function test() {
echo get_called_class()."\n";
}
}
class B extends A {
public static function test() {
parent::test();
}
}
A::test();
B::test(
Alexey Zakhlestin wrote:
On 11/26/07, Mike Lively <[EMAIL PROTECTED]> wrote:
I have come up with three different patches that allow us to work around
the issue of parent:: being considered an 'explicit class reference' and
thus disallowing static:: to effectively used.
The patches are against 5
PHP 6 Bug Database summary - http://bugs.php.net
Num Status Summary (62 total including feature requests)
===[*General Issues]==
26771 Suspended register_tick_funtions crash under threaded webservers
43408 Open get_called_class n
On 11/26/07, Stanislav Malyshev <[EMAIL PROTECTED]> wrote:
> > I believe this first patch is the proper way to go. It feels
> > "natural", "intuitive", etc.
>
> I don't see how making parent::foo() and A::foo() work differently is
> either "natural" or "intuitive".
A::foo() doesn't mean any inheri
I believe this first patch is the proper way to go. It feels
"natural", "intuitive", etc.
I don't see how making parent::foo() and A::foo() work differently is
either "natural" or "intuitive".
--
Stanislav Malyshev, Zend Software Architect
[EMAIL PROTECTED] http://www.zend.com/
(408)253-8829
On 11/26/07, Mike Lively <[EMAIL PROTECTED]> wrote:
> I have come up with three different patches that allow us to work around
> the issue of parent:: being considered an 'explicit class reference' and
> thus disallowing static:: to effectively used.
>
> The patches are against 5.3. I also have pat
PHP 4 Bug Database summary - http://bugs.php.net
Num Status Summary (627 total including feature requests)
===[*Compile Issues]==
43389 Open configure ignoring --without-cdb flag
===[*Pr
17 matches
Mail list logo
