• MORE:
  • Perl Camel
  • rss
  • GitHub logo
Perl.com
  •   ABOUT
  •   AUTHORS
  •   CATEGORIES
  • #
      TAGS

Ten Essential Development Practices

Jul 14, 2005 by Damian Conway

development
maintainable-perl
perl-best-practices
perl-development
perl-discipline
perl-style
serious-perl
style-guides
troubleshooting

The following ten tips come from Perl Best Practices, a new book of Perl coding and development guidelines by Damian Conway. 1. Design the Module’s Interface First The most important aspect of any module is not how it implements…

Read it

A Refactoring Example

Oct 9, 2003 by Michael Schwern

development
faster
optimization
perl
refactoring
speed
style-guides

About a year ago, a person asked the Fun With Perl mailing list about some code they had written to do database queries. It’s important to note that this person was posting from an .it address; why will become…

Read it

Program Repair Shop and Red Flags

Nov 14, 2000 by Mark-Jason Dominus

development
style-guides

What’s wrong with this picture? The Interface The Code open_info_file start_info_file start_next_part read_next_node Looking for the menu Putting It All Together Red Flags Don’t Repeat Code eof() return 0 and return undef Brief Confession What’s wrong with this picture?…

Read it
Page 1 of 1
Site Map
  • Home

  • About

  • Authors

  • Categories

  • Tags

Contact Us

To get in touch, send an email to perl.com-editor@perl.org, or submit an issue to perladvent/perldotcom on GitHub.

Perl Camel rss GitHub logo

License

This work is licensed under a Creative Commons Attribution-NonCommercial 3.0 Unported License.

Creative Commons License

Legal

Perl.com and the authors make no representations with respect to the accuracy or completeness of the contents of all work on this website and specifically disclaim all warranties, including without limitation warranties of fitness for a particular purpose. The information published on this website may not be suitable for every situation. All work on this website is provided with the understanding that Perl.com and the authors are not engaged in rendering professional services. Neither Perl.com nor the authors shall be liable for damages arising herefrom.