On Thu, Dec 8, 2011 at 2:43 PM, Fabrizio Giudici <[email protected]> wrote: > On Thu, 08 Dec 2011 20:27:24 +0100, Josh Berry <[email protected]> wrote: > > >> For API items, it works wonderfully. So did/do man pages for utility >> files. Most of us are not writing an API. > > > This could be not true, or subjective. A coarse-level decomposition of a > system into subsystems basically exposes APIs (if it's well done). I'm > thinking of both horizontal (tiers) and vertical (layers) decomposition. If > you're doing SOA, you're exposing APIs. In that domain, javadocs are pretty > good. Of course I agree that they aren't enough.
Agreed, and your last statement really highlights an assumption I had but did not voice. What I meant was that a sole reliance on javadoc as a documentation method causes more harm than is usually admitted. I had not meant to be pushing that javadocs should be abolished. Apologies for any confusion that angle may have caused. Also.... apologies if this went directly to you and not the group. I think I got "undo" hit before I was too late. When did these emails default reply to be direct to the person? -- You received this message because you are subscribed to the Google Groups "The Java Posse" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/javaposse?hl=en.
