-1 There's an official API doc mechanism called JavaDoc, so why twist or abuse it? Other documents like high level architecture overview, how-tos, etc. sure, why not, but leave a sound description of the code IN the code.
Werner On Sat, Mar 7, 2015 at 10:38 AM, Romain Manni-Bucau <[email protected]> wrote: > +-0 just need to be consistent without more cost even for migration > Le 7 mars 2015 10:34, "Oliver B. Fischer" <[email protected]> a > écrit : > > > Dear all, > > > > what do you think about using Asciidoctor for our JavaDoc? I think it > > offers better markup possibilities then pure JavaDoc. > > > > WDYT? > > > > Oliver > > > > -- > > N Oliver B. Fischer > > A Schönhauser Allee 64, 10437 Berlin, Deutschland/Germany > > P +49 30 44793251 > > M +49 178 7903538 > > E [email protected] > > S oliver.b.fischer > > J [email protected] > > X http://xing.to/obf > > > > >
