Closed Bug 581794 Opened 15 years ago Closed 6 years ago

Adjacent JSDoc comments cause incorrect line number

Categories

(Rhino Graveyard :: Core, defect)

x86
macOS
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED INACTIVE

People

(Reporter: micmath, Unassigned)

Details

User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10_6_4; en-us) AppleWebKit/533.16 (KHTML, like Gecko) Version/5.0 Safari/533.16 Build Identifier: Rhino 1.7 release 3 PRERELEASE 2010 03 24 If two JSDoc comments appear in the source code next to each other the line number of the second comment is wrong. In the example below there are 2 JSDoc comments, the first is at line 1, the second is at line 10. They are only separated by whitespace. This is perfectly valid in JSDoc, and in some cases is even required. ------------------ /** @fileOverview blah */ /** @function foo */ ------------------ Calling myAstNode.getLineno() for the second comment, returns 4 instead of 10. Reproducible: Always

Closing. Bug management is now done here:
https://github.com/mozilla/rhino

Status: UNCONFIRMED → RESOLVED
Closed: 6 years ago
Resolution: --- → INACTIVE
You need to log in before you can comment on or make changes to this bug.