omni360 / jsdoc-toolkit

Automatically exported from code.google.com/p/jsdoc-toolkit
0 stars 0 forks source link

Multiline comment may break the generated doc if it starts with a slash #340

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago
What steps will reproduce the problem?

1.Have some code which includes a multiline comment starting with a slash. For 
example:

foo.getUrl();/*/folder/folder/something*/

It seems the toolkit figures /*/ as a comment, and the remaining text 
(folder/folder/something/*/) as non commented code.

What is the expected output? What do you see instead?

Instead of the generated doc we expected, we noticed that many multiline 
comments were ignored by the toolkit, seemingly because it wasn't resolving 
were comments start and end after the offending /*/.

What version of the product are you using? On what operating system?

I'm using Windows 7 64 bit, with the latest toolkit release (2.4.0).

Original issue reported on code.google.com by CsRe...@gmail.com on 22 Aug 2012 at 3:13

GoogleCodeExporter commented 8 years ago
More information on this... the bug only happens if the string inside the 
multiline comment has no spaces.

Original comment by CsRe...@gmail.com on 23 Aug 2012 at 8:56