Path: csiph.com!v102.xanadu-bbs.net!xanadu-bbs.net!feeder.erje.net!eu.feeder.erje.net!newsfeed.datemas.de!uucp.gnuu.de!newsfeed.arcor.de!newsspool3.arcor-online.net!news.arcor.de.POSTED!not-for-mail Content-Type: text/plain; charset="ISO-8859-1" Message-ID: <26536832.LORQ4GdQbl@PointedEars.de> From: Thomas 'PointedEars' Lahn Reply-To: Thomas 'PointedEars' Lahn Organization: PointedEars Software (PES) Date: Thu, 19 Sep 2013 17:11:53 +0200 User-Agent: KNode/4.10.5 Content-Transfer-Encoding: 7Bit 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: 20 NNTP-Posting-Date: 19 Sep 2013 17:11:56 CEST NNTP-Posting-Host: c9dd66ae.newsspool4.arcor-online.net X-Trace: DXC=1>FINQNP050Tia]Ho99G504IUKA5<4 X-Complaints-To: usenet-abuse@arcor.de Xref: csiph.com comp.lang.javascript:21388 Cezary Tomczyk wrote: > On 2013-09-19 02:31, Stefan Weiss wrote: >> For those of you who write inline documentation blocks, what do you use >> to generate a user-readable API documentation from your source files? >> >> [ ] JSDoc > [...] > > I use JSDoc. Same here (Eclipse JSDT supports it natively to a certain extent), however because of its limitations I am working on a documentor of my own, based on the same syntax. -- PointedEars Twitter: @PointedEars2 Please do not Cc: me. / Bitte keine Kopien per E-Mail.