Hi all, One of the things that came out of my last thread was my lack of documentation, so now I'm keeping the documentation up-to-date as I make code changes.
I'm trying to come up with a decent layout for this. Tentatively, it looks like [1]. Does this appear to be acceptable? Could you recommend a perldoc or two in a style that you prefer for ideas? Also, because I don't want to end up with "analysis paralysis", sometimes I just have to start coding a module sub before I have a full understanding of how exactly I'm going to get to the end result with it. Are there any tricks you use (mental or code-wise) to help you down the road to prevent API changes, particularly on how you accept/name input parameters? One more thing, regarding those who prefer to code within the 72 column boundary...can you provide a couple of short examples as to your preferred indenting/wrapping format style when the need to wrap long lines of code? Cheers, Steve [1] - http://ipv6canada.com/perldoc_EagleUser-Ledger * This module is, and only will be internal to our company ** My wild use of references is solely so I can drill in their proper use/syntax
smime.p7s
Description: S/MIME Cryptographic Signature
