Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:37866
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: unknown (pb1.pair.com: domain php.net does not designate 85.214.94.56 as permitted sender)
Date: Sun, 25 May 2008 20:28:49 +0200
Reply-To: Marcus Boerger <helly@php.net>
Message-ID: <138099273.20080525202849@marcus-boerger.de>
To: internals@lists.php.net
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-15
Content-Transfer-Encoding: 8bit
Subject: [RFC] Change var_dump back?
From: helly@php.net (Marcus Boerger)

Hello Internals,

  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.

Best regards,
 Marcus