Re: /*global */
- As with the others that have commented.
I was very excited when this feature was introduced, and find it very useful.
I often have multiple js files that are compiled into one file during my build process.
The /*global */ feature allows me to use jslint without the headache of writing dummy declarations in each file.
I would hate to see this disappear.
--- In email@example.com, "Douglas Crockford" <douglas@...> wrote:
> I will be removing the /*global */ declarative comment. I am persuaded that it is best to explicitly use var to declare all global variables, even when accessing variables created by other compilation units.
> /*global */ will just be a comment.
- --- In firstname.lastname@example.org, "pauanyu" <pcxunlimited@...> wrote:
> "name" needs to be writable. It has no value by default,Which do you think is more likely, that a program wants to change the global name, or that a var name declaration in a function was forgotten? We won't get an implied global warning, but at least we can get a read only warning. I think that is the more useful default.
> but you can assign a string to it, indicating the name of
> the window/tab.