Closed Bug 373160 Opened 17 years ago Closed 12 years ago

Avoid using JS_GetFunctionName internally

Categories

(Core :: JavaScript Engine, enhancement)

Product:
Core
Component:
JavaScript Engine
Type:
enhancement
Priority:
Not set
Severity:
normal

Tracking

()

Status:
RESOLVED WORKSFORME

People

(Reporter: igor, Unassigned)

References

Details

JS_GetFunction has the same problem as JS_GetStringBytes/JS_GetStringChars: it does not take JSContext* parameter and ignores memory-allocation errors during string deflating.
(In reply to comment #0)
> JS_GetFunction has the same problem as JS_GetStringBytes/JS_GetStringChars: it
> does not take JSContext* parameter and ignores memory-allocation errors during
> string deflating.
> 

I meant JS_GetFunctionName.
Summary: Avoid using JS_GetFunction internally → Avoid using JS_GetFunctionName internally
Blocks: 373152
I am not working on the bug.
Assignee: igor → general
Is this ticket still valid? I did a quick grep for JS_GetFunctionName() and nothing came up in ...
Indeed, 'twas removed.
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.