For some Meta Programming tool for PHP that I am working on it would be
nice to have an additional object field in the array returned by
debug_backtrace() that contains a reference to the respective object on
the callstack.
After some looking into the zend_fetch_debug_backtrace() function I
Hi internals,
I was experimenting with different approaches of maintaining state and
serializing objects in PHP5. The problem is handling static class
members and static variables inside methods.
First, I noted that static variables inside methods are shared between
instances. C++ seems to
As you mentioned, static properties and statically scoped variables
don't belong to an object instance, so it doesn't make sense to
serialize them.
--Wez.
On 10/26/05, Matthias Pigulla [EMAIL PROTECTED] wrote:
Hi internals,
I was experimenting with different approaches of maintaining state
Work on the memcache pecl extension, I spoke with Antony Dovgal about this.
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
Any opinions?
Good code is code that's easy to debug (among other things). By
removing the Invalid argument supplied for foreach() warning without
providing mechanisms to turn it on, debugging code will be more
difficult. Logically speaking, when does it make sense to iterate over
something that
Hi
With PHP 5.1 knocking at the door, I guess many people would like to take
advantage og mysql 5 new features.
Best regards
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
Sebastian wrote:
Good code is code that's easy to debug (among other things). By
removing the Invalid argument supplied for foreach() warning without
providing mechanisms to turn it on, debugging code will be more
difficult. Logically speaking, when does it make sense to iterate over
something
On 26.10.2005 21:22, Holografix wrote:
Hi
With PHP 5.1 knocking at the door, I guess many people would like to take
advantage og mysql 5 new features.
What's the problem with MySQL 5 ?
Did you try ext/mysqli ( http://php.net/mysqli ) ?
--
Wbr,
Antony Dovgal
--
PHP Internals - PHP Runtime
On Wed, 2005-10-26 at 18:22 +0100, Holografix wrote:
With PHP 5.1 knocking at the door, I guess many people would like to take
advantage og mysql 5 new features.
I use PDO with MySQL 5 every day. What's the problem?
--
Jasper Bryant-Greene
General Manager
Album Limited
e: [EMAIL PROTECTED]
Hi
I know mysqli but already have some code (dao classes) based on pdo and I
would like to keep it.
Thanks anyway.
Best regards
holo
Antony Dovgal [EMAIL PROTECTED] escreveu na mensagem
news:[EMAIL PROTECTED]
On 26.10.2005 21:22, Holografix wrote:
Hi
With PHP 5.1 knocking at the door, I
Hi
I know mysqli but already have some code (dao classes) based on pdo and I
would like to keep it.
I am almost sure I read a message from Wez Furlong saying that pdo doesn't
actualy support mysql 5 sometime ago.
I will try it in a couple of hours. Now it's time to dinner and watch a
football
Hi
I know mysqli but already have some code (dao classes) based on pdo and I
would like to keep it.
I am almost sure I read a message from Wez Furlong saying that pdo doesn't
actualy support mysql 5 sometime ago.
I will try it in a couple of hours. Now it's time to dinner and watch a
football
Hello,
I have been trying to compile PHP with the namespaces patch, but have
been completely unable to find the time after an initial attempt failed
(I'm compiling on windows). So I just wanted to know what methods this
patch provides, if it does at all. Does it support import for example?
Hi
I am almost sure I read a message from Wez Furlong saying that pdo doesn't
actualy support mysql 5 sometime ago.
I will try it in a couple of hours. Now it's time to dinner and watch a
football game.
Thank you very much.
Best regards
holo
Holografix [EMAIL PROTECTED] escreveu na mensagem
What I said was something along the lines of me not going to knock
myself out with a beta version of mysql when we're trying to push out
a release.
Unless the client API seriously changed in mysql 5, there should be no
reason that PHP will stop working if you upgrade to mysql 5.
--Wez.
On
Kevin,
Just to make sure, you can get the latest patch from
http://www.zend.com/zend/week/pat/pat44.txt. For documentation, please
refer to this post: http://news.php.net/php.internals/17484.
Let me know if you have any questions or if you still cannot get the patch
to compile (I wrote the patch
On Wed, 26 Oct 2005, Sebastian wrote:
[clip]
Good code is code that's easy to debug (among other things). By
removing the Invalid argument supplied for foreach() warning without
providing mechanisms to turn it on, debugging code will be more
difficult.
[clip]
You got to the point here.
Jani Taskinen wrote:
On Wed, 26 Oct 2005, Sebastian wrote:
[clip]
Good code is code that's easy to debug (among other things). By
removing the Invalid argument supplied for foreach() warning without
providing mechanisms to turn it on, debugging code will be more
difficult.
[clip]
Von: Wez Furlong [mailto:[EMAIL PROTECTED]
As you mentioned, static properties and statically scoped
variables don't belong to an object instance, so it doesn't
make sense to serialize them.
Ok, but on the other hand they are just variables - so the question was
if there is any (possibly
Greg Beaver wrote:
amen, this behavior makes no sense even though sizeof() is an alias to
count(). sizeof('this') and sizeof('this long thing') are both 1, which
makes no sense. I would go so far as to say a E_NOTICE is more
appropriate than E_STRICT - you should only be using count() for
pdo_mysql is not version specific, it'll work with 3.23,4.0,4.1 and even
5.0 version of MySQL.
Ilia
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
Ilia Alshanetsky schrieb:
pdo_mysql is not version specific, it'll work with 3.23,4.0,4.1 and even
5.0 version of MySQL.
Well, now it is not anymore. I had to wait several months not being able
to use PDO because my Windows/XAMPP was already using MySQL 4.1 and the
PDO betas were _not_
On 27.10.2005 01:58, Oliver Grätz wrote:
Ilia Alshanetsky schrieb:
pdo_mysql is not version specific, it'll work with 3.23,4.0,4.1 and even
5.0 version of MySQL.
Well, now it is not anymore. I had to wait several months not being able
to use PDO because my Windows/XAMPP was already using
Do you read the posts you're commenting on?
I said there _were_ (there are not anymore) problems with PDO betas on
_Windows_ systems (that was a PECL build for PHP 5.0.3). This was not a
complaint on anything and I didn't complain then because it was beta and
not meant to be used with PHP 5.0.x,
Ilia Alshanetsky wrote:
IMHO this is a bad idea, if you really wanted to support NULL in a
particular case you, as a developer could do:
php -r '$n=NULL; foreach((array)$n as $v);'
Making NULL usage transparent where array is expects will lead to
difficult to debug code.
hi :-)
the warning
Ilia Alshanetsky wrote:
Greg Beaver wrote:
amen, this behavior makes no sense even though sizeof() is an alias to
count(). sizeof('this') and sizeof('this long thing') are both 1, which
makes no sense. I would go so far as to say a E_NOTICE is more
appropriate than E_STRICT - you should only
Oliver Grätz wrote:
Do you read the posts you're commenting on?
I said there _were_ (there are not anymore) problems with PDO betas on
_Windows_ systems (that was a PECL build for PHP 5.0.3). This was not a
complaint on anything and I didn't complain then because it was beta and
not meant to
27 matches
Mail list logo
