Namespaces as Sugar (was: complexity tax)

[Mike Shaver]

2008/5/27 Maciej Stachowiak <mjs at apple.com>:
> It could save a lot of complexity, by not requiring any first-class support
> for namespace lookup on arbitrary objects.

Is the expectation then that having two lookup models, one for global
objects and the other for non-global objects, going to provide less
complexity?

In a browser, "window" is the global object; would property lookup on
"window" be namespaced when referenced as such?  When you have a
handle to another window?  When you use |this.prop| in a global
function?

If we have namespace-aware lookup, it seems to me that it would be
less complex for implementors and script authors alike for it to
always apply, rather than just for one magical object.

Mike