Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:6685 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 36068 invoked by uid 1010); 23 Dec 2003 09:10:58 -0000 Delivered-To: ezmlm-scan-internals@lists.php.net Delivered-To: ezmlm-internals@lists.php.net Received: (qmail 36044 invoked by uid 1007); 23 Dec 2003 09:10:58 -0000 Message-ID: <20031223091058.36043.qmail@pb1.pair.com> To: internals@lists.php.net Date: Tue, 23 Dec 2003 10:13:21 +0100 Lines: 13 User-Agent: KNode/0.7.2 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7Bit X-Posted-By: 62.177.160.38 Subject: discrepancy tokens windows binary vs source tarball 4.3.4 From: dkphp@ntec.nl (Dick van der Kaaden) Hi, I noticed that the php.net windows binaries for php 4.3.4 are compiled against a newer version of the token table then is in the source tarball for php 4.3.4. If you compile php 4.3.4 by hand a T_INLINE_HTML returns 308 where as the windows binary from php.net will return 309. This causes extensions using the tokenizer contants that are compiled from the 4.3.4 source to fail (or at least be incompatible) on windows systems where the binary is installed. - Dick