note 82384 deleted from function.json-decode by danbrown

Note Submitter: Hayley Watson ---- @AMA3: "It's strange that forward-slash is permitted to be escaped but not required to be, and that it has the same meaning either way, but that's how it's written, and so shall it be." JavaScript ignores '\' characters that don't start any sort of escape sequence, so as far as it is concerned, "\/" is equivalent to "/" (ECMA-262, §7.8.4). So in that sense it's permitted but not required to be: so why do it? json_encode("</script>") will produce "<\/script>" so that HTML parsers don't see a </script> end tag and choke on it (to play it safe and simplify the implementation, it escapes all '/'s); json_decode() therefore has to cope with that. As for it being necessary, I agree: it isn't on MY machine :) json_decode('{"a":"<p>test<\/p>"}'); ==> (object)array('a' => '<p>test</p>'); json_decode('{"a":"<p>test</p>"}'); ==> (object)array('a' => '<p>test</p>');