Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:9902 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 27010 invoked by uid 1010); 17 May 2004 18:15:08 -0000 Delivered-To: ezmlm-scan-internals@lists.php.net Delivered-To: ezmlm-internals@lists.php.net Received: (qmail 26986 invoked by uid 1007); 17 May 2004 18:15:08 -0000 Message-ID: <20040517181508.26985.qmail@pb1.pair.com> To: internals@lists.php.net Reply-To: "l0t3k" Date: Mon, 17 May 2004 14:15:11 -0400 Lines: 28 X-Priority: 3 X-MSMail-Priority: Normal X-Newsreader: Microsoft Outlook Express 6.00.2800.1409 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1409 X-Posted-By: 69.15.15.204 Subject: Minor Zend Engine Niggle From: cshmoove@hotmail.com ("l0t3k") ive noticed in all the OOP extensions callbacks for properties that the "member" (property name) is not guaranteed to be a string zval. is there a reason for this, given that any other type should have choked the lexer in the first place ? even if not, then can the casting be done in the engine as opposed to the extensions ? what im referring to is the common idiom if (member->type != IS_STRING) { tmp_member = *member; zval_copy_ctor(&tmp_member); convert_to_string(&tmp_member); member = &tmp_member; } ...... if (member == &tmp_member) { zval_dtor(member); } in read_property and write_property handlers. l0t3k