On 7 Jun 2007, at 23:04, Matisse Enzer wrote:
I wonder how you all feel these days about the "put the pod at the __END__" approach? I've been trying it for over a year now and am not really sure its the best way to go (vs. having the pod for each method right next to it.)
I'd like an editor that lets me look at it either way. Sometimes I want to look at uninterrupted code - in which case interleaved documentation just gets in the way. Other times it's nice to be able to read the code while documenting it - in which case interleaved would be better.
Actually I could probably live with a program that collected all the documentation and assembled it correctly at the end of the file. Then I could write the initial documentation for a method inline and shift it to the end once I'm finished referring to the code.
So: Interleaved for the first draft, at the end for maintenance. -- Andy Armstrong, hexten.net
