Whether Sharp Variable use is really deprecated?

[biju]

with about:config
javascript.options.strict = true
At Tools > Error Console I get following warning

==== Error Console ====

Warning: deprecated #1= usage
Source File: chrome://adblock/content/ajax-intercept.js
Line: 80, Column: 12
Source Code:
ajaxCheck: #1=function(request) {

----------------------------------------------------------------------------------------

Warning: deprecated #1# usage
Source File: chrome://adblock/content/ajax-intercept.js
Line: 109, Column: 22
Source Code:
onModifyRequest : #1#, // yum, sharp-variables

==== Error Console End ====

Whether Sharp Variable use is really deprecated?

[bre...@mozilla.org]

Maybe we should get rid of those warnings, or change them to say
"non-portable usage".

Neither uneval nor toSource and sharp variables are being proposed to
ECMA TG1, so these are not going to show up in other implementations
unless popular demand moves the several implementors to do the work; at
that point, standardization will be easy.

/be

[biju]

bre...@mozilla.org wrote:
> Maybe we should get rid of those warnings, or change them to say
> "non-portable usage".

Thanks..
submitted https://bugzilla.mozilla.org/show_bug.cgi?id=367600