On Thu, December 7, 2006 9:17 am, Zeev Suraski wrote: > At 13:35 07/12/2006, Stefan Esser wrote: >>Guys, >> >>why can't you simply introduce a new variable type for serialized >>strings like uppercase S: >>There is absolutely no need for breaking backward compatibility. > > I can't think of a single reason not to use a new type like you > suggest. > > Can anybody think of any drawbacks?
Somebody MIGHT have written their own unserializer/serializer which made incorrect assumptions about the internal format, such as 's' being the same as 'S'... So, perhaps, just to be consistent with the data I *think* appears in serialized form, 'u' for 'unicode' would maybe be better than 'S' I confess I have no idea what is actually inside of serialized data, and could be WAY off base, but I stretched far enough to come up with something that could go wrong, because that's the kind of paranoid guy I am. :-) -- Some people have a "gift" link here. Know what I want? I want you to buy a CD from some starving artist. http://cdbaby.com/browse/from/lynch Yeah, I get a buck. So? -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
