Ed wrote: > One: throw a parse time error if more than one used vocabulary exports the > same name which is in turn used by the using vocabulary.
Maybe the way to proceed is to turn on this check and see what happens to the codebase. :-) Let's suppose that a vocabulary is changed which triggers the shadow possibility error in many other vocabularies. OK, the owners of those vocabularies go and add RESOLVE: forms to fix the problem. Then later the owner of the original vocabulary decides that it had too much of an impact and decides to undo the shadow; she puts the offending word in a private namespace or renames it. Now you have a bunch of unnecessary RESOLVE: forms laying around. This is similar to the problem of unnecessary items in a USING: list. Have you thought much about how to handle this? Is it too agressive to throw a parse error if USING: or RESOLVE: refers to a superfluous items? It would actually help me in cleaning up my USING: lists. :-) Ed ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ Factor-talk mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/factor-talk
