Text.ParserCombinators.* is a bad name

[Sebastian Sylvan]

On 3/8/06, Donald Bruce Stewart <dons at cse.unsw.edu.au> wrote:
> * Firstly, a library naming issue. Text.ParserCombinators feels like a
> clunkey name. This week I was working on a set of regex combinators,
> that ideally would go under:
>
>     Text.Combinators.Regex
>
> but we're stuck with Text.ParserCombinators.Regex. Making me think that:
>
>     Text.ParserCombinators.ReadP
>     Text.ParserCombinators.Parsec
>     Text.PrettyPrint.HughesPJ
>
> namespace should be deprecated in favour of:
>
>     Text.Combinators.ReadP
>     Text.Combinators.Parsec
>     Text.Combinators.HughesPJ
>
> Reflecting the wide variety of text-manipulation combinators we use.
> The latter seem more elegant. Parsec in particular can lead to some
> noisy import statements in its current namespace.
>

Why do we need the "Combinators" bit at all? Will we really have so
many different kind of parsers and other text manipulation tools that
we need to separate them based on their technique?
I'd rather have

Text.Parsers.Parsec

Or even just

Text.Parsec

/S
--
Sebastian Sylvan
+46(0)736-818655
UIN: 44640862