Closed
Bug 367600
Opened 19 years ago
Closed 13 years ago
change jsconsole warning message for Sharp Variables
Categories
(Core :: JavaScript Engine, enhancement)
Tracking
()
RESOLVED
WORKSFORME
People
(Reporter: BijuMailList, Unassigned)
References
Details
change jsconsole warning message for Sharp Variables
see http://groups.google.com/group/mozilla.dev.tech.js-engine/browse_thread/thread/4e39d83ad50516a8
currently with about:config
javascript.options.strict = true
we get warning for usage of Sharp Variables
as "Warning: deprecated #1= usage"
instead of "deprecated usage" say "non-portable usage".
Comment 1•19 years ago
|
||
Is it possible to configure SM not to create sharp variables to get a source code, that is reusable to create a clone in a new session (after shut down and restart).
Comment 2•19 years ago
|
||
(In reply to comment #1)
> Is it possible to configure SM not to create sharp variables to get a source
> code, that is reusable to create a clone in a new session (after shut down and
> restart).
Without sharp variables you can't uneval to source that, when eval'ed again, results in an isomorphic object graph. There's no other way to express cycles and join-points in general.
/be
![]() |
||
Comment 3•13 years ago
|
||
Sharp variables were removed.
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → WORKSFORME
You need to log in
before you can comment on or make changes to this bug.
Description
•