Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:1365 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 57543 invoked from network); 7 May 2003 21:42:34 -0000 Received: from unknown (HELO vckyb1.nw.wakwak.com) (211.9.230.144) by pb1.pair.com with SMTP; 7 May 2003 21:42:34 -0000 Received: from at.wakwak.com (at.wakwak.com [211.9.230.135:25]) by vckyb1.nw.wakwak.com (Postfix) with ESMTP id 851E73FE1C; Thu, 8 May 2003 06:42:33 +0900 (JST) Received: from at.wakwak.com (z84.211-19-95.ppp.wakwak.ne.jp [211.19.95.84]) by at.wakwak.com (8.12.9/8.12.9/2003-03-31) with SMTP id h47LgXH5025839; Thu, 8 May 2003 06:42:33 +0900 (JST) (envelope-from moriyoshi@at.wakwak.com) Date: Thu, 08 May 2003 06:45:31 +0900 X-Mailer: EdMax Ver2.85.3F MIME-Version: 1.0 To: John Coggeshall Cc: internals@lists.php.net Message-ID: <20030508064531KBJ4MQ@at.wakwak.com> Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit In-Reply-To: <1052329731.13471.6.camel@localhost.localdomain> References: <1052329731.13471.6.camel@localhost.localdomain> Subject: Re: [PHP-DEV] IS_TYPE in zend_compile.c From: moriyoshi@at.wakwak.com (Moriyoshi Koizumi) Marcus apparently left to the conference with the build broken. My workaround: $ cvs diff -r 1.414 Zend/zend_compile.c | patch -p0 -R Moriyoshi John Coggeshall wrote: > About 16 hours ago it looks like someone modified zend_compile.c to fix > a bug... the current head has around line 1161 (clean CVS checkout): > > if (type_hint->op_type == IS_TYPE) { > opline->opcode = ZEND_VERIFY_TYPE; > } else { > opline->opcode = ZEND_VERIFY_INSTANCEOF; > } > > But now i can't seem to compile it anymore... where is IS_TYPE defined? > I'm assuming if it exists at all, it has to have been in the engine for > awhile looking at the commit times (zend_compile.c is the only file > modified in the past 16 hours)... either way, neither myself or the > compiler can find it. > > Perhaps there is just something broken about my system... but I thought > I'd make sure before I went on a goose chase. > > John