I prefer not to surround optional argument with brackets (or any other stuff that is typical of unix man pages) because those have real meanings in Perl. Likewise, I don't really like the pseudocode argument style of "perldoc -f" (i.e. all caps), though that's at least a sort of reference standard.
I prefer to use actual perl structures, named in a way that indicates what they should contain, and then explain them in the actual Pod description. E.g.
=head2 validate $is_valid = validate( \@args ); C<validate()> takes a reference to an array of arguments...
But I'll echo what the others said -- consistency is the most important thing. You'll never get everyone to agree on a form to use, but as long as you're internally consistent, you'll minimize confusion.
-xdg
Code written by xdg and posted on PerlMonks is public domain. It is provided as is with no warranties, express or implied, of any kind. Posted code may not have been tested. Use of posted code is at your own risk.
In reply to Re: POD conventions
by xdg
in thread POD conventions
by eff_i_g
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |