On Nov 27, 2003, at 8:41 AM, Christian Schneider wrote:
Marcus Boerger wrote:
He doesn't say that. We are doing a lot of work on the QA front and of
course fix bugs and release new versions. But our policy is to
introduce
Ok, I declare it a bug then so you can include it in the next bug fix
rele
Marcus Boerger wrote:
He doesn't say that. We are doing a lot of work on the QA front and of
course fix bugs and release new versions. But our policy is to introduce
Ok, I declare it a bug then so you can include it in the next bug fix
release. The point about not being able to compile it on thous
Hello Christian,
Thursday, November 27, 2003, 2:23:16 PM, you wrote:
> Derick Rethans wrote:
>> No, what I said was correct. As it is very unlikely that we create a new
>> PHP 4 minor version we CAN not at a new function as it's impossible to
>> modify source that has already been compiled on tho
Derick Rethans wrote:
No, what I said was correct. As it is very unlikely that we create a new
PHP 4 minor version we CAN not at a new function as it's impossible to
modify source that has already been compiled on thousands of machines.
So no more bug fixes either? That's serious stuff and quite in
On Thu, 27 Nov 2003, Christian Schneider wrote:
> [This is off-list]
(not anymore)
> Derick Rethans wrote:
> > We can not add a new function to PHP 4 anyway... so there is no other
> > acceptable solution...
>
> Should be "We do not WANT to add a new function to PHP4".
No, what I said was corre
On Thu, 27 Nov 2003, Christian Schneider wrote:
> Björn Schotte wrote:
> > I think they solve the problem exactly the way Wez told you.
>
> Which means everyone has to reinvent the wheel. Ok, fine with me.
We can not add a new function to PHP 4 anyway... so there is no other
acceptable solution..
Björn Schotte wrote:
I think they solve the problem exactly the way Wez told you.
Which means everyone has to reinvent the wheel. Ok, fine with me.
- Chris
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
Hi Christian,
* Christian Schneider wrote:
> If you read my original posting you'll notice that I've already done
> this but I thought other people have exactly the same problem.
I think they solve the problem exactly the way Wez told you.
--
Schnellanbindung an 350 Standorte?! CaseStudy anfor
Wez Furlong wrote:
Why not add your own clone() function to your apps;
If you read my original posting you'll notice that I've already done
this but I thought other people have exactly the same problem.
Looks like I was wrong.
- Chris
--
PHP Internals - PHP Runtime Development Mailing List
To un
Hey Christian,
Why not add your own clone() function to your apps;
something like this:
if (version_compare(phpversion(), "5.0", "<")) {
function clone($object) { return $object; }
} else {
function clone($object) { return $object->__clone(); }
}
then (re)write all your code to call clon
Derick Rethans wrote:
Just use an auto_prepend which sets the implicit_clone option... no
problems then anymore.
*Sigh*
Looks like you're not reading my postings really.
This means your migration path to ref on assignement semantics is:
1) current code, copy (PHP4)
2) wait months for PHP5 to be r
On Thu, 27 Nov 2003, Christian Schneider wrote:
> Marcus Boerger wrote:
> > If i get you right you want to have __clone() for PHP4, too right? But
> > that's already to late.
>
> That's what I was told when I was asking for ref on assignment for PHP4.
> And now we have to go through this hassle
Marcus Boerger wrote:
If i get you right you want to have __clone() for PHP4, too right? But
that's already to late.
That's what I was told when I was asking for ref on assignment for PHP4.
And now we have to go through this hassle for PHP5. I simply cannot
believe noone thought of this problem
Hello Christian,
Thursday, November 27, 2003, 11:51:06 AM, you wrote:
> Andi Gutmans wrote:
>> You can use the zend2.implicit_clone INI directive (change it at
>> run-time if you want at the beginning of the application).
> But I do want to move my application to the new semantics, I think it i
Andi Gutmans wrote:
You can use the zend2.implicit_clone INI directive (change it at
run-time if you want at the beginning of the application).
But I do want to move my application to the new semantics, I think it is
much more reasonable than the PHP4 behaviour anyway (sadly enough my
request to
At 11:00 AM 11/27/2003 +0100, Christian Schneider wrote:
Andi Gutmans wrote:
issues and many of them might be solvable (using the already existing
compatibility mode for object cloning or by other means).
Could we please, please, please have a way of cloning objects which works
in both versions?
16 matches
Mail list logo
