The clarity gained by a more readable standard is often eclipsed by the confusion for people encountering it for the first time. Unless your audience is small, this might not be worth it.
Alternatively, if you're persuaded you need something better, shop around for existing alternatives. Javadoc style (package.name#method) comes to mind, and there's a chance people coming across your docs will already be familiar with that. On Wed, Aug 15, 2012 at 10:57 AM, sawyer x <[email protected]> wrote: > On Wed, Aug 15, 2012 at 7:54 AM, Shmuel Fomberg > <[email protected]>wrote: > >> >> I find it easier on the eye to see what part is the module, and what is >> the function. >> this oppose to the perl-code notation of Module::Name::function_name. >> > > I'm quite comfortable with that because of the clear naming convention > there. > I think yours is equally (if not more) readable. > > _______________________________________________ > Perl mailing list > [email protected] > http://mail.perl.org.il/mailman/listinfo/perl > -- Gaal Yahas <[email protected]> http://gaal.livejournal.com/
_______________________________________________ Perl mailing list [email protected] http://mail.perl.org.il/mailman/listinfo/perl
