System.File.Open
System.File.Write
System.Net.WebRequest
So naturally, you get like things grouped together. Assuming your language has a sane library, your concern shouldn't be an issue.Of course, if your "library" consists of 4000 functions named things like "mysql_get_connect" and "DateFormatUTC", then yes, you're screwed.
What you want are examples sorted by usage.
An object, function, etc, can only be in exactly one namespace. e.g. "File" or "Net", but not both. What if a class can be used to accomplish multiple goals? The example code will end up in some obscure corner of your deeply-linked language reference pages.
No... a single .html file that contains all examples in all categories (or namespaces in your case) is much more useful than any alphabetical reference.
Note that the single examples.html page does not try to provide a reference. It provides example code, and that's it. No noise.
Sorry for the misunderstanding.
I'd rather have a listing of examples by category.
Such as:
An alphabetical list of classes is like an alphabetical listing of tools in a toolbox. It's like, great, but how do I use them?