Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:19450
Return-Path: <helly@php.net>
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Delivered-To: mailing list internals@lists.php.net
Received: (qmail 33706 invoked by uid 1010); 6 Oct 2005 18:07:53 -0000
Delivered-To: ezmlm-scan-internals@lists.php.net
Delivered-To: ezmlm-internals@lists.php.net
Received: (qmail 33690 invoked from network); 6 Oct 2005 18:07:53 -0000
Received: from unknown (HELO lists.php.net) (127.0.0.1)
  by localhost with SMTP; 6 Oct 2005 18:07:53 -0000
X-Host-Fingerprint: 81.169.182.136 ajaxatwork.net Linux 2.4/2.6
Received: from ([81.169.182.136:38898] helo=strato.aixcept.de)
	by pb1.pair.com (ecelerity 2.0 beta r(6323M)) with SMTP
	id 98/6A-54476-8F765434 for <internals@lists.php.net>; Thu, 06 Oct 2005 14:07:53 -0400
Received: from [192.168.1.3] (dslb-084-063-020-121.pools.arcor-ip.net [84.63.20.121])
	(using TLSv1 with cipher AES256-SHA (256/256 bits))
	(No client certificate requested)
	by strato.aixcept.de (Postfix) with ESMTP id E0AB935C392;
	Thu,  6 Oct 2005 20:08:52 +0200 (CEST)
Date: Thu, 6 Oct 2005 20:07:58 +0200
Reply-To: Marcus Boerger <helly@php.net>
X-Priority: 3 (Normal)
Message-ID: <1723219575.20051006200758@marcus-boerger.de>
To: Andrei Zmievski <andrei@gravitonic.com>
Cc: Ilia Alshanetsky <iliaa@php.net>, Dmitry Stogov <dmitry@php.net>,
	Derick Rethans <derick@php.net>, Andi Gutmans <andi@zend.com>,
	<internals@lists.php.net>, Andrei Zmievski <andrei@php.net>
In-Reply-To: <50fd2bb20ec265926a6f81c9c6895a5d@gravitonic.com>
References: <609160853.20051006011445@marcus-boerger.de>
	<50fd2bb20ec265926a6f81c9c6895a5d@gravitonic.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Subject: Re: Question regarding test system
From: helly@php.net (Marcus Boerger)

Hello Andrei,

  transparent == doesn't really matter. And if you insist, will you write
all the tests and maintain them?

marcus

Thursday, October 6, 2005, 7:21:31 PM, you wrote:

> 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




Best regards,
 Marcus