Re: [ZEND-ENGINE-CVS] cvs: ZendEngine2 / zend_API.c

From: Date: Sun, 03 Aug 2003 10:05:44 +0000
Subject: Re: [ZEND-ENGINE-CVS] cvs: ZendEngine2 / zend_API.c
References: 1 2 3 4 5  Groups: php.zend-engine.cvs 
Request: Send a blank email to php-zend-engine-cvs+get-1579@lists.php.net to get a copy of this message
Hello Zeev, Sunday, August 3, 2003, 12:07:28 PM, you wrote: ZS> At 12:51 03/08/2003, Marcus Börger wrote: >>Hello Zeev, >> >>Sunday, August 3, 2003, 9:13:53 AM, you wrote: >> >>ZS> At 04:04 03/08/2003, Marcus Börger wrote: >> >>Sure, look into my next patch :-) >> >>ZS> What next patch..? >> >>The reflection patch that shows the function/method parameters. ZS> Can you be more specific about which parts it uses that aren't initialized? >>But anyway uninitialized variables or struct parts are a bad idea because >>sooner or later something will make use of it. ZS> Well, I don't really agree about that. It goes back to the same argument ZS> about covering up or finding the actual problems. We initialize everything ZS> that's supposed to be initialized with a meaningful value, which doesn't ZS> necessarily have to be zero. A zero initialization may just cover up a ZS> real bug where we don't initialize something that's supposed to be ZS> initialized with a meaningful value (it may not, too, but it's a possibility). The thing i need to initialize is at least op_array.opcodes but i think that any pointer should be initialized to NULL in such structs. And when i looked into the stucts during debugging i thought that it would make more sense to zero initialize the whole struct instead of searching for some elements. -- Best regards, Marcus mailto:helly@php.net

« previous php.zend-engine.cvs (#1579) next »