brian d foy wrote:
> I don't read the documentation. If I need to do that to understand the
> name, it's probably not a good name.
>
----
Totally understand that -- if you are looking through a page of
module names and the 44 byte summaries was more what I was thinking, as
that's the only thing you have a chance of being able to easily browse
(too bad we can't think of an easier way to make such things easier to
browse)
But the 1 line summary is normally what you'd see; The module name
alone very
rarely enough to tell you what the module does. Admittedly, I didn't
put that
in the original subject, but it is in the summary line. I dunno about
you, but
I almost always read that, since when you search on cpan, you see:
*mem* <http://search.cpan.org/%7Elawalsh/mem-0.3.1/lib/mem.pm>
use in-"mem"ory version of (calling) module & define immediate
---
Maybe I'll lost the define immediate part as I don't think that's clear
enough to give a hint about what it means -- leave that for the docs;
Sides,
that's more of a side effect of 'use' than part of mem.
So something like:
mark "in-'mem'" package as already loaded
> Having said that, I've reached the end of what I can do for you., so
> I'm dropping out of the conversation.
>
----
Your comments were useful. A good 1 liner is important.
> Good luck, :)
>
Thanks!
