Re: [PROPOSAL] add a leading backslash to classname when serializing/var_exporting

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