commit or don't, fixed for a client, that code is just stupid bogus.
-sterling
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
Hi,
On Thu, 1 Jul 2004 06:17:07 +0100
Wez Furlong [EMAIL PROTECTED] wrote:
Even better, if you do discover something that might be exploitable,
you should keep your mouth shut and instead send mail to
[EMAIL PROTECTED] where, among a handful of others, Stefan will also
read your message.
Sure if it's a fix I think it should go in.
At 11:25 PM 6/30/2004 -0700, Sterling Hughes wrote:
commit or don't, fixed for a client, that code is just stupid bogus.
-sterling
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
--
PHP
committed to head and branch.
On Wed, 30 Jun 2004 23:43:05 -0700, Andi Gutmans [EMAIL PROTECTED] wrote:
Sure if it's a fix I think it should go in.
At 11:25 PM 6/30/2004 -0700, Sterling Hughes wrote:
commit or don't, fixed for a client, that code is just stupid bogus.
-sterling
On 2004/07/01, at 14:25, Andi Gutmans wrote:
Hi Moriyoshi,
The object handle is not a unique identifier. Different object types
(e.g. PHP objects, SimpleXML objects) can have the same object handle.
The real unique identifier is object handle + object handlers array or
more useful in your case,
this would still not suffice for a proper serialization, overloaded
objects should have serialize and unserialize handlers something
for 5.1 methinks.
-sterling
On Thu, 1 Jul 2004 16:03:09 +0900, Moriyoshi Koizumi
[EMAIL PROTECTED] wrote:
On 2004/07/01, at 14:25, Andi Gutmans wrote:
Toby:
On Thu, Jul 01, 2004 at 10:57:18AM +0200, Tobias Schlitt wrote:
Hi Christian Wenz! You wrote:
* Using pre on view.php is probably not a good idea (TM, again), since
in that case longer lines are not wrapped automatically (see id=61).
True. I will either change that to a div with
Sorry, wrong list.
(I've got to change my aliases so I don't do this again...)
--Dan
--
T H E A N A L Y S I S A N D S O L U T I O N S C O M P A N Y
data intensive web and database programming
http://www.AnalysisAndSolutions.com/
4015 7th Ave #4, Brooklyn
This is the new one. Hope it is ready to commit this time.
http://www.voltex.jp/patches/bug28325-preliminary-20040701.patch.diff
Two untidy bitshifts are intended to form an atomic bit rotation and
are somewhat necessary for the uniqueness of the hash value.
At least 31 object handles of the same
Andi Gutmans wrote:
The object handle is not a unique identifier.
Are there any plans on implementing a really unique identifier to
objects? This would, among other things, allow objects to be used as
array keys.
--
Sebastian Bergmann
http://sebastian-bergmann.de/
Hello Sterling,
i have that on my personal 5.1 todo list since months...
marcus
Thursday, July 1, 2004, 6:29:53 PM, you wrote:
this would still not suffice for a proper serialization, overloaded
objects should have serialize and unserialize handlers something
for 5.1 methinks.
Hello,
It is too early to do anything concrete, but I wonder if PHP 5.1 or
later could add a non-fatal version of throw to handle
warnings/errors/notices.
A trigger_error() that accepted an object similar to Exception would be
a good solution. This way, all the benefits of the Exception class
Hi:
In PHP 4, when using exec() multiple times with the same array in the
output parameter, the data from subsequent exec() calls appended the new
results to the existing array. This is as the manual says.
When PHP 5 first came out, each call to exec() overwrote the prior array.
At some
13 matches
Mail list logo
