The existence of sequences.lib, combinators.lib and so on always bothered me, and I was opposed to the idea from the very start, because instead of thinking about the right place to put a utility word, people would just dump them in there. So we ended up with an ad-hoc grab-bag of utilities with no consistency, documentation or tests. Many of them were not used, and didn't even work correctly. Over time the useful and clean words were split off into their own vocabularies or moved into core, and code in basis/ and extra/ that used the *.lib vocabularies was refactored to use the new words, or in some cases, not need them.
Now that nothing in basis/ and extra/ used them anymore, I put them in unmaintained/, and this is where they will stay. If you see some words in there that are useful, and there is no clean way to express your code without them, and you don't want to just have a copy of these words in your own vocabulary as a private utility, then we can consider moving them into a new vocabulary, or even the core. But I don't want to return to having these vocabularies of random, poorly-documented and poorly-tested utilities that end up cluttering the language only to save a few tokens here and there. Slava On Fri, Dec 19, 2008 at 7:28 AM, Alex Drummond <[email protected]> wrote: > Hi, > > I was just wondering what's going on with the removal of the > sequences.lib vocabulary. Some useful words like reduce* seem to have > been lost. Is there any particular reason for removing these rather > than moving them to another vocab? ------------------------------------------------------------------------------ _______________________________________________ Factor-talk mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/factor-talk
