The default bug view has changed. See this FAQ.

Make js_ValueToAtom's signature more normal (return JSAtom* rather than bool+redundant JSAtom** outparam)

RESOLVED FIXED in mozilla16

Status

()

Core
JavaScript Engine
--
minor
RESOLVED FIXED
5 years ago
5 years ago

People

(Reporter: Waldo, Assigned: Waldo)

Tracking

unspecified
mozilla16
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

(Whiteboard: [js:t])

Attachments

(1 attachment)

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

This is practically trivial rs=-land, but for an API change I feel like I should record a bug for it, probably.
Attachment #633629 - Flags: review?(sphink)
Comment on attachment 633629 [details] [diff] [review]
Patch

Review of attachment 633629 [details] [diff] [review]:
-----------------------------------------------------------------

r+ on the change, r- on the bug title. This creates js::ToAtom, which follows the pattern of js::ToObject and js::ToString, but differs from js::ToNumber, js::ToUint32, js::ToInteger, js::ToPrimitive, and every JSAPI function that takes an initial JSContext* and returns a bool. I don't know how many calls we have that take a leading JSContext*, return non-bool, and might set a pending exception.

(That said, I'm fine with the change.)
Attachment #633629 - Flags: review?(sphink) → review+
Whiteboard: [js:t]
https://hg.mozilla.org/mozilla-central/rev/94dd2b2a8216
Status: ASSIGNED → RESOLVED
Last Resolved: 5 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla16
You need to log in before you can comment on or make changes to this bug.