Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:37871 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 43687 invoked from network); 25 May 2008 20:30:02 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 25 May 2008 20:30:02 -0000 Authentication-Results: pb1.pair.com smtp.mail=foolistbar@googlemail.com; spf=pass; sender-id=pass Authentication-Results: pb1.pair.com header.from=foolistbar@googlemail.com; sender-id=pass; domainkeys=bad Received-SPF: pass (pb1.pair.com: domain googlemail.com designates 64.233.182.184 as permitted sender) DomainKey-Status: bad X-DomainKeys: Ecelerity dk_validate implementing draft-delany-domainkeys-base-01 X-PHP-List-Original-Sender: foolistbar@googlemail.com X-Host-Fingerprint: 64.233.182.184 nf-out-0910.google.com Received: from [64.233.182.184] ([64.233.182.184:65313] helo=nf-out-0910.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 79/01-21001-84CC9384 for ; Sun, 25 May 2008 16:30:02 -0400 Received: by nf-out-0910.google.com with SMTP id b11so821528nfh.13 for ; Sun, 25 May 2008 13:29:58 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=gamma; h=domainkey-signature:received:received:from:to:in-reply-to:subject:x-priority:references:message-id:content-type:content-transfer-encoding:mime-version:date:cc:x-mailer; bh=A5UX1k4nYvnvnIqdDmqq4IOhZUUXNgVMgYi/0xqTlGI=; b=AGfW2XnD+EQxrJnfEmxiF6P5Hx15ouvN0sfzMuhypH5et0bdh8ngUa6z/WwtNAxMgL1ftFnswlJUmNuasJbFv6tpRHKjDeJbybilYqS4vL7BRJ0xWR2YfNfj9aN5dVipLrbaNUfcAX/rE6XjpjS3TaYT5yPPNSziTkeT46I7SKw= DomainKey-Signature: a=rsa-sha1; c=nofws; d=googlemail.com; s=gamma; h=from:to:in-reply-to:subject:x-priority:references:message-id:content-type:content-transfer-encoding:mime-version:date:cc:x-mailer; b=OE66q0GM6myfDPeI2VPjZ1LvRZFNLVDy1sJtdcV03LyF5aCCpB72v3RqFQniqRaCY+urWyvVSDS8HadJsuoti1n5EFAe1FzG/taXVZsyFqLQi5JJS4+ftfAge0qHGZQYTCYeEzLfAj7XhQH9CsFclXTLzrGbpOCR6CDI8yLA6xY= Received: by 10.210.29.11 with SMTP id c11mr1779603ebc.16.1211747398007; Sun, 25 May 2008 13:29:58 -0700 (PDT) Received: from ?192.168.0.116? ( [217.44.35.200]) by mx.google.com with ESMTPS id f4sm24719113nfh.0.2008.05.25.13.29.56 (version=TLSv1/SSLv3 cipher=RC4-MD5); Sun, 25 May 2008 13:29:57 -0700 (PDT) To: Marcus Boerger In-Reply-To: <138099273.20080525202849@marcus-boerger.de> X-Priority: 3 (Normal) References: <138099273.20080525202849@marcus-boerger.de> Message-ID: <4FBECEFB-9051-4584-83D1-5FB9C27CB704@googlemail.com> Content-Type: text/plain; charset=WINDOWS-1252; format=flowed; delsp=yes Content-Transfer-Encoding: quoted-printable Mime-Version: 1.0 (Apple Message framework v919.2) Date: Sun, 25 May 2008 21:29:54 +0100 Cc: internals@lists.php.net X-Mailer: Apple Mail (2.919.2) Subject: Re: [PHP-DEV] [RFC] Change var_dump back? From: foolistbar@googlemail.com (Geoffrey Sneddon) On 25 May 2008, at 19:28, Marcus Boerger wrote: > 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) =20 > "foo"' > as it is the new string type and change the other output to show =20 > 'binary' > which it is now? I'd say that var_dump("foo") should give 'unicode(3) "foo"' and =20 var_dump(b"foo") should give 'binary(3) "foo"'. I see no reason not to =20= give the explicit type =97 why would anything rely on this for backwards = =20 compatibility? -- Geoffrey Sneddon