> > But more difficult is comments like this: > > // Blah blah blah here is a list: > > // * blah blah blah > > // * blah blah blah blah > > // * blah blah Hmm. Javadoc would let you encode lists as <ul> <li> ... <li> ... </ ul> which would be nice, though I suppose not critical. Seems that you could just pass the html through, though.
> Garbage in, garbage out ;) So you would get a multi-line comment with > a different number of whitespaces in front of each line (maybe with > the common number of whitespaces (i.e. one) removed from all of them, > as suggested above). Yeah. Not to repeat my other message, but @param @return etc. are important things for the accessors/setters/etc. Otherwise this won't be able to generate documentation that IDEs will find useful. Documenting private fields is of limited use, IMO. and in a lot of cases aren't even translated to the final documentation. -- You received this message because you are subscribed to the Google Groups "Protocol Buffers" group. To post to this group, send email to proto...@googlegroups.com. To unsubscribe from this group, send email to protobuf+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/protobuf?hl=en.
