Re: /*global */
- --- In firstname.lastname@example.org, "Randall Lee Spence" <analogueweb@...> wrote:
>It really make sens to use extern because that exactly what they are.
> --- In email@example.com, "Douglas Crockford" <douglas@> wrote:
> > One thing I can do is to add more Assume options supporting popular Ajax libraries. If you are responsible for a popular Ajax library with a small, stable list of predefined globals, then give me the list.
> For library authors managing separate files and combing at runtime,
> what about using the old /*extern */ declaration? That seems
> like it would be a reasonable compromise. Just a thought.
> - Randall Lee Spence
In my Scripts most of the entries in /*global*/ are not Global variables.
- --- 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.