Re: [PHP-DEV] compiling own extension for php-5.1.1

2006-01-03 Thread Antony Dovgal
On 03.01.2006 06:26, Marco Glatz wrote: hello, i am trying to port a self-written extension from php-5.0.2 to php-5.1.1, if i try to load the extension i get an error: ext/php_webcontrol.dll doesn't appear to be a valid Zend extension You're using zend_extension=php_webcontrol.dll, while you

Re: [PHP-DEV] compiling own extension for php-5.1.1

2006-01-03 Thread Marco Glatz
Antony Dovgal <[EMAIL PROTECTED]> schrieb am 03.01.06 12:01:16: > > On 03.01.2006 06:26, Marco Glatz wrote: > > hello, > > > > i am trying to port a self-written extension from php-5.0.2 to php-5.1.1, > > if i try to load the extension i get an error: > > > > ext/php_webcontrol.dll doesn't app

[PHP-DEV] debugging APC - bit over my head; clue desired

2006-01-03 Thread Jochem Maas
hi guys, a while back I was asking about APC - I have a problem with php seghfaulting when I use APC _and_ turn on the opcode cache (apc_store() and apc_fetch() work very well - I'm sticking _lots_ of 'ResultSet' objects in there for instance and it works very nicely) but turning the opcode cache

Re: [PHP-DEV] debugging APC - bit over my head; clue desired

2006-01-03 Thread Rasmus Lerdorf
Jochem Maas wrote: a while back I was asking about APC - I have a problem with php seghfaulting when I use APC _and_ turn on the opcode cache (apc_store() and apc_fetch() work very well - I'm sticking _lots_ of 'ResultSet' objects in there for instance and it works very nicely) Note that cachi

[PHP-DEV] [PATCH] Bring the Zend Engine copyright notice up to date

2006-01-03 Thread Steph Fox
Index: ZendEngine2/zend.c === RCS file: /repository/ZendEngine2/zend.c,v retrieving revision 1.330 diff -u -r1.330 zend.c --- ZendEngine2/zend.c 1 Dec 2005 11:49:15 - 1.330 +++ ZendEngine2/zend.c 3 Jan 2006 18:07:22 -

[PHP-DEV] Fw: interesting buglet

2006-01-03 Thread Steph Fox
built: Jan 3 2006 00:05:59) Copyright (c) 1997-2006 The PHP Group Zend Engine v2.1.0, Copyright (c) 1998-2005 Zend Technologies Guess we need to force display_startup_errors = 0? Or is there some way to make PHP know these are internal classes? - Steph __ NOD32 1.1350 (20060103) I

[PHP-DEV] CVS Account Request: ssuceveanu

2006-01-03 Thread Stefan Suceveanu
maintain Validate_RO subclass -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php

[PHP-DEV] Re: CVS Account Request: ssuceveanu

2006-01-03 Thread Pierre
On Tue, 3 Jan 2006 12:25:33 -0800 [EMAIL PROTECTED] ("Stefan Suceveanu") wrote: > maintain Validate_RO subclass confirmed --Pierre -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php

[PHP-DEV] __call overload detection

2006-01-03 Thread Andrew Yochum
Currently there is no way to detect if the __call overloads a particular method. Property overloading has __isset now in 5.1 - maybe for method overloading the equivalent should be something like __iscallable. Maybe method_exists should remain as is, as the method won't ever really exist but is_c

Re: [PHP-DEV] __call overload detection

2006-01-03 Thread Andrew Yochum
Hi Marcus, On Tue, Jan 03, 2006 at 10:06:56PM +0100, Marcus Boerger wrote: > Hello Andrew, > > right now you can use reflection. > > marcus The reflection APIs do not help I believe. Consider that one may only want __call to respond to a computable set of overloaded method names. Right now,

Re: [PHP-DEV] __call overload detection

2006-01-03 Thread Marcus Boerger
Hello Andrew, you do not implement __call for a method but you deal with the method name in any sense you like, which also includes ignoring specific __call invocations. Reflection gives you the ability to check whetehr a function is being physically available. If you need more it is up to you t

Re: [PHP-DEV] Fw: interesting buglet [PATCH]

2006-01-03 Thread Steph Fox
ss we need to force display_startup_errors = 0? Or is there some way to make PHP know these are internal classes? - Steph __ NOD32 1.1350 (20060103) Information __ This message was checked by NOD32 antivirus system. http://www.eset.com -- PHP Internals - PHP Runtime Dev

Re: [PHP-DEV] __call overload detection

2006-01-03 Thread Mike Naberezny
Hi Andrew, Andrew Yochum wrote: Consider that one may only want __call to respond to a computable set of overloaded method names. Usually, this is done by something like this: throw new Exception('Call to undefined method ' . __CLASS__ . '::' . $method . '()'); }

Re: [PHP-DEV] __call overload detection

2006-01-03 Thread Andi Gutmans
Why not just use Reflection API to check? It seems quite trivial to do so. At 12:57 PM 1/3/2006, Andrew Yochum wrote: Currently there is no way to detect if the __call overloads a particular method. Property overloading has __isset now in 5.1 - maybe for method overloading the equivalent should

Re: [PHP-DEV] __call overload detection

2006-01-03 Thread Mike Naberezny
Marcus Boerger wrote: If you need more it is up to you to provide the infrastructure. Remember we will not in anyway allow __call to handle inheritance. Hi Marcus, If one is determined enough, at least visibility can be faked by exception trace introspection. Below demonstrates protected, re

Re: [PHP-DEV] __call overload detection

2006-01-03 Thread Marcus Boerger
Hello Andi, the point is probably that there is no way in determinig whether a certain function is supposed to work prior to calling it. regards marcus Wednesday, January 4, 2006, 12:45:23 AM, you wrote: > Why not just use Reflection API to check? It seems quite trivial to do so. > At 12:57

Re: [PHP-DEV] __call overload detection

2006-01-03 Thread Andrew Yochum
Hi Marcus, On Tue, Jan 03, 2006 at 10:50:24PM +0100, Marcus Boerger wrote: > Hello Andrew, > > you do not implement __call for a method but you deal with the method name > in any sense you like, which also includes ignoring specific __call > invocations. Reflection gives you the ability to chec

Re: [PHP-DEV] __call overload detection

2006-01-03 Thread Andi Gutmans
Right but you can do it in user-land. If you're writing __call() you could add an additional method to see if it's mapped. I don't think it's quite as common as isset(). At 04:05 PM 1/3/2006, Marcus Boerger wrote: Hello Andi, the point is probably that there is no way in determinig whethe

Re: [PHP-DEV] __call overload detection

2006-01-03 Thread Marcus Boerger
Hello Andrew, you got everything correct and i see your point, so you may want to open a feature request under bugs.php.net. marcus Wednesday, January 4, 2006, 1:37:26 AM, you wrote: > Hi Marcus, > On Tue, Jan 03, 2006 at 10:50:24PM +0100, Marcus Boerger wrote: >> Hello Andrew, >> >> you

Re: [PHP-DEV] __call overload detection

2006-01-03 Thread Marcus Boerger
Hello Andi, we didn't saw any necessaty for __isset either. marcus Wednesday, January 4, 2006, 1:41:44 AM, you wrote: > Right but you can do it in user-land. If you're writing __call() you > could add an additional method to see if it's mapped. I don't think > it's quite as common as isset(

Re: [PHP-DEV] __call overload detection

2006-01-03 Thread Andi Gutmans
I think it's different especially as it's complementary to unset() but I don't intend to get into an argument about it. In any case, the tools for Andrew to resolve this programmatically on the PHP level exist even if the syntax isn't 100% of what he'd like it to be. Over and out. Andi At 05:

[PHP-DEV] CVS Account Request: taak

2006-01-03 Thread Nicholas Pisarro
New PEAR package. I made a mistake with the username in request last week, it should have been taak, same as in PEAR. Pierre confirmed the request. Package name: Text_LanguageDetect -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php

Re: [PHP-DEV] __call overload detection

2006-01-03 Thread Andrew Yochum
On Tue, Jan 03, 2006 at 03:44:33PM -0800, Mike Naberezny wrote: > I see your point with detection by something like __is_callable(), although > I can't personally think of a place where I'd use it. Consider a situation where a proxy/mediator/broker class implementing __call proxyies method calls

Re: [PHP-DEV] __call overload detection

2006-01-03 Thread Andrew Yochum
On Tue, Jan 03, 2006 at 05:29:11PM -0800, Andi Gutmans wrote: > I think it's different especially as it's complementary to unset() > but I don't intend to get into an argument about it. I see your point there about isset and unset being a matched pair. From my perspective, call is similar to uns

Re: [PHP-DEV] __call overload detection

2006-01-03 Thread Mike Naberezny
Andrew Yochum wrote: Consider a situation where a proxy/mediator/broker class implementing __call proxyies method calls to other classes (possibly of 3rd party origins), which themselves may or may not implement __call. You'd like the broker itself to have a consistent behavior for the sake of i

Re: [PHP-DEV] __call overload detection

2006-01-03 Thread Andrew Yochum
On Wed, Jan 04, 2006 at 02:23:51AM +0100, Marcus Boerger wrote: > Hello Andrew, > > you got everything correct and i see your point, so you may want to open a > feature request under bugs.php.net. > > marcus Thanks. Will do. Regards, Andrew -- Andrew Yochum Plexpod [EMAIL PROTECTED] 718-360

Re: [PHP-DEV] __call overload detection

2006-01-03 Thread Andrew Yochum
Hi Mike, On Tue, Jan 03, 2006 at 06:05:31PM -0800, Mike Naberezny wrote: > Hi Andrew, > > I understand your scenario and I agree but I think that this would be > better done in userland by implementing an interface. > > Remember that all of the magic methods do not need to be declared, i.e. you

Re: [PHP-DEV] debugging APC - bit over my head; clue desired

2006-01-03 Thread Jochem Maas
Rasmus Lerdorf wrote: Jochem Maas wrote: a while back I was asking about APC - I have a problem with php seghfaulting when I use APC _and_ turn on the opcode cache (apc_store() and apc_fetch() work very well - I'm sticking _lots_ of 'ResultSet' objects in there for instance and it works very n

Re: [PHP-DEV] __call overload detection

2006-01-03 Thread Sebastian Bergmann
Mike Naberezny schrieb: > If one is determined enough, at least visibility can be faked by > exception trace introspection. You do not need exceptions for this, just use debug_backtrace(). -- Sebastian Bergmann http://www.sebastian-bergmann.de/ GnuPG Key: 0xB85B5D69 / 27A7