in reply to Re: Re: Perl Programming guidelines/rules
in thread Perl Programming guidelines/rules

1) * # method: getExitCode() This just replicates the sub getExitCode { line.

Yes, it does. That's because I used the simplest possible example for the sake of brevity in this writeup.

2) Email. I work for a small company that's had a lot of management turnover. I want credit for my code. I also want to make it easy for a new hire to find me if they have questions. I still remember the afternoon I spent wandering around trying to find out who wrote an obscure chunk of code.

3) # return : int And most of my co-workers use C. Int mostly serves to contrast from returning a string, array, hash, hash ref, or whatever else I may use.

I recently inherited a major chunk of code from a departed engineer. It was his discipline in using this commenting format that made it possible for me to figure out what he was doing. After years of inheriting spaghetti code, I appreciate a little discipline. Don't get me started on the "Perl Coder" who didn't understand arrays and refused to use them.

-Logan
"What do I want? I'm an American. I want more."

  • Comment on Re: Re: Re: Perl Programming guidelines/rules