Remove JS_BeginJSONParse, JS_ConsumeJSONText, JS_FinishJSONParse

RESOLVED FIXED in mozilla6

Status

()

Core
JavaScript Engine
RESOLVED FIXED
6 years ago
6 years ago

People

(Reporter: Waldo, Assigned: Waldo)

Tracking

Trunk
mozilla6
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

(Whiteboard: fixed-in-tracemonkey)

Attachments

(1 attachment)

Created attachment 525831 [details] [diff] [review]
Patch

We have JS_ParseJSON and JS_ParseJSONWithReviver which are much simpler to use.  Also, at the moment the old APIs use the old JSON parser almost by necessity, and making them use the new parser is somewhat hard.  (Nothing in Mozilla uses the old APIs, only the new ones, so web pages/etc. only ever see behavior according to the new parser -- *not* multiple different parsers.)

This patch just removes the API entry points.  It doesn't remove the old parser yet because it's still possible there might end up some strong reason to revert (and we couldn't just make the necessary change to the new parser).  That can be for later once we're comfortable with the new parser, don't see too much reason to rush it (I'm the only one having to deal with an extra 600 lines of code in json.cpp these days, really).
Attachment #525831 - Flags: review?(brendan)
Attachment #525831 - Flags: review?(brendan) → review+
http://hg.mozilla.org/tracemonkey/rev/f7eaddcc2abf
Whiteboard: fixed-in-tracemonkey
Target Milestone: --- → mozilla6
http://hg.mozilla.org/mozilla-central/rev/f7eaddcc2abf
Status: ASSIGNED → RESOLVED
Last Resolved: 6 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.