Closed
Bug 373152
Opened 18 years ago
Closed 12 years ago
Deprecating JS_GetStringBytes, JS_GetStringChars and JS_GetFunctionName
Categories
(Core :: JavaScript Engine, enhancement)
Core
JavaScript Engine
Tracking
()
RESOLVED
WORKSFORME
People
(Reporter: igor, Unassigned)
References
Details
[This is a spin-off of bug 366725] The functions JS_GetStringBytes and JS_GetStringChars are the only string functions that do not take JSContext* while accessing runtime structures/allocating memory. We should deprecate their usage and provides alternatives either through different names or through some ifdefs.
Reporter | ||
Updated•18 years ago
|
Depends on: 373160
Summary: Deprecating JS_GetStringBytes and JS_GetStringChars → Deprecating JS_GetStringBytes, JS_GetStringChars and JS_GetFunctionName
Comment 2•14 years ago
|
||
Has this been affected by bug 609440?
Reporter | ||
Comment 3•14 years ago
|
||
(In reply to comment #2) > Has this been affected by bug 609440? No - that bug still provides access to the char array.
![]() |
||
Comment 4•12 years ago
|
||
2 of these have been removed (I think by Igor). JS_GetStringChars has been split into infallible and fallible cx-taking versions.
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → WORKSFORME
You need to log in
before you can comment on or make changes to this bug.
Description
•