Path: csiph.com!v102.xanadu-bbs.net!xanadu-bbs.net!feeder.erje.net!eu.feeder.erje.net!eweka.nl!lightspeed.eweka.nl!193.141.40.65.MISMATCH!npeer.de.kpn-eurorings.net!npeer-ng0.de.kpn-eurorings.net!newsfeed.arcor.de!newsspool3.arcor-online.net!news.arcor.de.POSTED!not-for-mail Content-Type: text/plain; charset="UTF-8" Message-ID: <137966624.Mj0kYfID6r@PointedEars.de> From: Thomas 'PointedEars' Lahn Reply-To: Thomas 'PointedEars' Lahn Organization: PointedEars Software (PES) Date: Thu, 19 Sep 2013 17:55:20 +0200 User-Agent: KNode/4.10.5 Content-Transfer-Encoding: 8Bit X-Face: %i>XG-yXR'\"2P/C_aO%~;2o~?g0pPKmbOw^=NT`tprDEf++D.m7"}HW6.#=U:?2GGctkL,f89@H46O$ASoW&?s}.k+&. MIME-Version: 1.0 Lines: 23 NNTP-Posting-Date: 19 Sep 2013 17:55:20 CEST NNTP-Posting-Host: c9dd66ae.newsspool4.arcor-online.net X-Trace: DXC=\P^GLL^17[5QbA1[CgMQ004IUK For those of you who write inline documentation blocks, what do you use > to generate a user-readable API documentation from your source files? > > […] > [ ] I just write the doc blocks, the rest is not my concern > [ ] this is useless for JavaScript/ECMAScript/... > [ ] I don't use anything like that, but want to check a box anyway > [ ] what are inline documentation blocks? > [ ] inline API documentation is WRONG > [ ] comments are for the weak > [ ] your logic is flawed > > If I haven't covered all possible choices, just tell me what I missed. YMMD :) -- PointedEars Twitter: @PointedEars2 Please do not Cc: me. / Bitte keine Kopien per E-Mail.