Closed
Bug 630370
Opened 14 years ago
Closed 7 years ago
self-host Object.watch()
Categories
(Core :: JavaScript Engine, defect)
Tracking
()
RESOLVED
DUPLICATE
of bug 638054
People
(Reporter: gal, Unassigned)
References
(Depends on 1 open bug)
Details
Attachments
(1 file)
2.67 KB,
application/x-javascript
|
Details |
watchpoints incur some nasty complexity in our code base and are non-standard. We might be able to self-host a mechanism that offers almost the same features but doesn't require any specialized runtime support in the VM.
Comment 1•14 years ago
|
||
\o/
Reporter | ||
Comment 2•14 years ago
|
||
This is not as powerful as the native watch and has a bunch of corner cases (most notably it is not persistent across property deletions), but maybe its enough to deprecate the real watch code?
Comment 3•12 years ago
|
||
See also bug 638054 for removing Object.prototype.watch.
Comment 4•12 years ago
|
||
With the infrastructure tracked by bug 784288, we could implement this in a safe way.
Depends on: 784288
Comment 5•12 years ago
|
||
Object.watch is on its way to being removed in favor of a debugger-only alternative (bug 638054), so it might not be worth investing a lot of effort on this bug unless the fate of Object.watch changes.
Assignee | ||
Updated•10 years ago
|
Assignee: general → nobody
Comment 6•7 years ago
|
||
watch() was removed in bug 638054.
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•