[PATCH 2/4] qh: Fall for peer pressure from myself, and implement some help

[robin.sonefors at op5.com]

> First off, the nerd channel list must be generated dynamically. We
> have them in a handy array, so we might as well print them all 
> while we're at it. If we make it possible to provide a description
> string when creating the channel we can print that too and the help
> API for the nerd channel is pretty much complete.

Right. Sure. I guess I was just wary of API modifications, but no problem to do
so. Split that into it's own patch.

> Why not just 'help'? That way people can do what's natural
> with text interfaces and try "@nerd help" and they would still get the
> same response, whereas typing "@nerd --help" into an interactive text
> listener seems less intuitive.

My reasoning was to have something obscure enough that it would be unlikely to
clash with other commands. I realize now that was pretty crappy reasoning -
what else would be called "help"?

Note that this feedback affects the first patch in my last patch series, so
I've changed that patch, rather than change it in a new patch on top of that
one.

In other words, these three patches replace the first two patches in the old
series, but the last two in the last series still applies. I'll do things
differently if you tell me how.


------------------------------------------------------------------------------
Keep yourself connected to Go Parallel: 
INSIGHTS What's next for parallel hardware, programming and related areas?
Interviews and blogs by thought leaders keep you ahead of the curve.
http://goparallel.sourceforge.net