in reply to Re^2: Reporting a Bug in Core Documentation
in thread Reporting a Bug in Core Documentation

I get the feeling that you're implying something

Mostly just informational. Only that it may be intentional to treat the two modules as a single package.

That's not to say it would not be better if both modules were treated separately; or at least both mention in the section header.

I'm also unsure whether it is worth changing a delta document that becomes (kind of) redundant with the next release. But then again, a report might mean an improvement if the package requires a mention in the next delta.

As far as I am aware (but don't definitively know; hence why I didn't comment on that first time around), perlbug is the right vehicle for doc changes. But I'd wait for someone who has had one accepted (or one of those that might accept or reject them) to reply before going ahead with it.


With the rise and rise of 'Social' network sites: 'Computers are making people easier to use everyday'
Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error.
"Science is about questioning the status quo. Questioning authority".
In the absence of evidence, opinion is indistinguishable from prejudice.
  • Comment on Re^3: Reporting a Bug in Core Documentation