One thing to consider: I would expect IDEs to help with this. For example, Eclipse does a pretty good job of letting one forget that one has to import things before one can use them.
On Oct 15, 2012, at 17:27 , Brendan Eich <[email protected]> wrote: > Have to say I agree with Kevin and Yehuda here, on implicit declaration (not > export or import) being better. Not saying I'm sold on the whole idea, but I > feel the pain. > > The module-wide scope is pretty much Dart. Anyone using Dart much want to > comment on how that's worked out? > > /be > > Yehuda Katz wrote: >> >> Yehuda Katz >> (ph) 718.877.1325 >> >> >> On Mon, Oct 15, 2012 at 4:19 PM, Kevin Smith <[email protected] >> <mailto:[email protected]>> wrote: >> >> >> For the case of importing "37" at-names, I would expect that * >> imports would take care of it: >> >> import * from ModuleDefining37NameInterface; >> >> >> Oh, come on! >> >> The problem isn't importing the names. The problem lies in having >> to maintain a nightmarishly long set of declarations which are >> **completely internal to the module**, not exported and not imported. >> >> >> This is essentially the problem I had when I tried to port existing code. It >> was especially annoying because it was easy to forget to create and maintain >> the declarations. >> >> The more I think about it, the more I think that scoping symbols to modules >> would work well. Does that mean symbols are simply disallowed outside of >> modules? >> >> >> Kevin >> >> >> _______________________________________________ >> es-discuss mailing list >> [email protected] >> https://mail.mozilla.org/listinfo/es-discuss > _______________________________________________ > es-discuss mailing list > [email protected] > https://mail.mozilla.org/listinfo/es-discuss > -- Dr. Axel Rauschmayer [email protected] home: rauschma.de twitter: twitter.com/rauschma blog: 2ality.com
_______________________________________________ es-discuss mailing list [email protected] https://mail.mozilla.org/listinfo/es-discuss
