Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:19445 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 16893 invoked by uid 1010); 6 Oct 2005 17:22:49 -0000 Delivered-To: ezmlm-scan-internals@lists.php.net Delivered-To: ezmlm-internals@lists.php.net Received: (qmail 16878 invoked from network); 6 Oct 2005 17:22:49 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 6 Oct 2005 17:22:49 -0000 X-Host-Fingerprint: 216.145.54.171 mrout1.yahoo.com FreeBSD 4.7-5.2 (or MacOS X 10.2-10.3) (2) Received: from ([216.145.54.171:20835] helo=mrout1.yahoo.com) by pb1.pair.com (ecelerity 2.0 beta r(6323M)) with SMTP id BE/88-54476-86D55434 for ; Thu, 06 Oct 2005 13:22:49 -0400 Received: from [66.228.175.145] (borndress-lm.corp.yahoo.com [66.228.175.145]) by mrout1.yahoo.com (8.13.4/8.13.4/y.out) with ESMTP id j96HLDCm048019; Thu, 6 Oct 2005 10:21:13 -0700 (PDT) In-Reply-To: <609160853.20051006011445@marcus-boerger.de> References: <609160853.20051006011445@marcus-boerger.de> Mime-Version: 1.0 (Apple Message framework v623) Content-Type: text/plain; charset=US-ASCII; format=flowed Message-ID: <50fd2bb20ec265926a6f81c9c6895a5d@gravitonic.com> Content-Transfer-Encoding: 7bit Cc: Ilia Alshanetsky , Dmitry Stogov , Derick Rethans , Andi Gutmans , internals@lists.php.net, Andrei Zmievski Date: Thu, 6 Oct 2005 10:21:31 -0700 To: Marcus Boerger X-Mailer: Apple Mail (2.623) Subject: Re: Question regarding test system From: andrei@gravitonic.com (Andrei Zmievski) It has nothing to do with the encoding. var_dump() outputs the value type, which is 'string' for native strings and 'unicode' for Unicode strings. I don't see why we should merge the two. -Andrei On Oct 5, 2005, at 4:14 PM, Marcus Boerger wrote: > Hello guys, > > i had a chat with Dmitry this morning regarding the unpleasant state > of > our test system. I assume here that everyone agrees that it is quite > difficult to provide each and every test expectations in two variants, > one > for native string executoin (e.g. unicode_semantics=off) and one for > unicode > execution (e.g. unicode_semantics=on). The easy way out is to have > var_dump > not print 'unicode' for namely values but instead use 'string' always. > Since > the encoding is meant to be transparent anyway there shouldn't be a > problem. > And in case we have tests where the difference is important we can > overwrite > the setting in the --INI-- setting and use the --UEXPECT-- as we are > doing > now. Dmitry now came up with the idea of providing a new ini setting to > control this behavior. He suggests to name it > "var_dump.show_unicode=on/off" > Any comments? > > > Best regards, > Marcus