Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:67018 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 25371 invoked from network); 9 Apr 2013 20:08:21 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 9 Apr 2013 20:08:21 -0000 Authentication-Results: pb1.pair.com header.from=smalyshev@sugarcrm.com; sender-id=pass Authentication-Results: pb1.pair.com smtp.mail=smalyshev@sugarcrm.com; spf=pass; sender-id=pass Received-SPF: pass (pb1.pair.com: domain sugarcrm.com designates 108.166.43.115 as permitted sender) X-PHP-List-Original-Sender: smalyshev@sugarcrm.com X-Host-Fingerprint: 108.166.43.115 smtp115.ord1c.emailsrvr.com Linux 2.6 Received: from [108.166.43.115] ([108.166.43.115:53391] helo=smtp115.ord1c.emailsrvr.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id C6/D3-07032-43574615 for ; Tue, 09 Apr 2013 16:08:21 -0400 Received: from localhost (localhost.localdomain [127.0.0.1]) by smtp7.relay.ord1c.emailsrvr.com (SMTP Server) with ESMTP id 242A91B8099; Tue, 9 Apr 2013 16:08:18 -0400 (EDT) X-Virus-Scanned: OK Received: by smtp7.relay.ord1c.emailsrvr.com (Authenticated sender: smalyshev-AT-sugarcrm.com) with ESMTPSA id D5EAF1B811B; Tue, 9 Apr 2013 16:08:17 -0400 (EDT) Message-ID: <51647536.6030108@sugarcrm.com> Date: Tue, 09 Apr 2013 16:08:22 -0400 Organization: SugarCRM User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:17.0) Gecko/20130328 Thunderbird/17.0.5 MIME-Version: 1.0 To: Laruence CC: PHP Internals References: In-Reply-To: Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Subject: Re: [PHP-DEV] [PROPOSAL] add a leading backslash to classname when serializing/var_exporting From: smalyshev@sugarcrm.com (Stas Malyshev) Hi! > I proposal to add a leading backslash to all classnames (not only ns > names, since no harm, consistent and make sense) when doing serialize, > var_export etc. I'm not sure what this has to do with serialize. For var_export it may be useful but the use case looks kind of limited. I can't think of a common case where such change would be beneficial, and since it's a BC break I don't think it is worth it, unless we can find a real use case where it is necessary. In the original bug, it says that the user would use var_export in different namespace, but why would you need to do this? -- Stanislav Malyshev, Software Architect SugarCRM: http://www.sugarcrm.com/ (408)454-6900 ext. 227