>>"And as a user of an api, would you rather read the code or the javadoc ? "
>The code, in general. It's more likely to be correct. If the code looks bad then the javadoc *might* clarify the intent but commit messages are more likely to be accurate assuming you don't have a 'Latest changes' guy on the team. That seems like a pretty bold claim to make in general. javadoc can be pretty useful for getting a bird's eye view of the big api, then zooming in to what you need. That's nice for a variety of reasons, such as comparing two similar libraries. -- You received this message because you are subscribed to the Google Groups "Java Posse" group. To post to this group, send email to javaposse@googlegroups.com. To unsubscribe from this group, send email to javaposse+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/javaposse?hl=en.
