Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:19426
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Date: Thu, 6 Oct 2005 01:14:45 +0200
Reply-To: Marcus Boerger <helly@php.net>
Message-ID: <609160853.20051006011445@marcus-boerger.de>
To: Andi Gutmans <andi@zend.com>, Andrei Zmievski <andrei@php.net>,
	Derick Rethans <derick@php.net>, Dmitry Stogov <dmitry@php.net>,
	Ilia Alshanetsky <iliaa@php.net>
Cc: internals@lists.php.net
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Subject: Question regarding test system
From: helly@php.net (Marcus Boerger)

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