Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:37867
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: softfail (pb1.pair.com: domain zend.com does not designate 64.97.136.187 as permitted sender)
Message-ID: <00cb01c8be98$d36be870$4401a8c0@foxbox>
Reply-To: "Steph Fox" <steph@zend.com>
To: "Marcus Boerger" <helly@php.net>,
	<internals@lists.php.net>
References: <138099273.20080525202849@marcus-boerger.de>
Date: Sun, 25 May 2008 19:54:54 +0100
Organization: Zend Technologies
MIME-Version: 1.0
Content-Type: text/plain;
	format=flowed;
	charset="iso-8859-15";
	reply-type=original
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] [RFC] Change var_dump back?
From: steph@zend.com ("Steph Fox")

Hi Marcus,

>  now that we got rid of the unicode.semantics switch, should we change
> var_dump("foo") from showing 'unicode(3) "foo"' back to 'string(3) "foo"'
> as it is the new string type and change the other output to show 'binary'
> which it is now? And long those lines should we change all occurances of
> the 'u' prefix to instead show a 'b' prefix if non usnice? All in all I
> would prefer to reflect the real situation, the new string type is unicode
> capable but named 'string' and the old stuff is binary data and hence
> called 'binary'. And when entering strings we have a b prefix but no u
> prefix. This would affect a ton of tests but we need to fix run-tests and
> most tests anyway. For one, we need to drop all --UEXPECT*-- blocks.

I have about 3000 tests ready to commit, but obviously if 'u'/'unicode' is 
going too there'll be a bit more work to do on them.

I've covered Zend/tests, /tests and a chunk of ext/standard/tests over the 
last week.

- Steph

>
> Best regards,
> Marcus
>
>
> -- 
> PHP Internals - PHP Runtime Development Mailing List
> To unsubscribe, visit: http://www.php.net/unsub.php
>