Maybe. Maybe not. Only he can confirm if it indeed is a genuine oversight or not.
But since this behaviour is quite clearly documented in the POD for the module, and that the module has been around for almost a decade now, I'm not convinced the behaviour is due to an oversight. But again, the POD could be wrong or script-generated.
Only Graham or P5P can give us a definite, authoritative statement for the reasons his module behaves the way it does, until then, it's play by the rules in the POD, i suppose?
perl -e '$,=$",$_=(split/\W/,$^X)[y[eval]]]+--$_],print+just,another,split,hack'er