Hello everyone, if I may insert my opinion on this matter:
I think the way to really minimize this "extra baggage" problem
is for the "using" system to enforce (or "strongly encourage",
at least) the explicit naming of words.
eg. if vocabulary X uses vocabulary A, then X must explicitly
name each of the words from A that it needs.
Then A can be expanded with any number of extra words and it won't
ever affect X.
It's just like proper functional programming without side effects.
You name your input parameters, and you only work with them in
the function body.
Regards, and apologies if I misunderstand the situation.
Anton Rolls.
Eduardo Cavazos wrote:
> Let's say vocabularies X Y Z use vocabulary A. I edit A. I refresh-all. Let's
> suppose that 'refresh-all' has the proposed behaviour whereby it refreshes X
> Y and Z since they depend on A
> So this is going to lead to a situation where I am constrained about how I
> name things in my vocabulary based on how *others* use it. The whole freedom
> to name is now impeded a bit.
> 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
Factor-talk@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/factor-talk
