[jira] Created: (QDOX-168) Parsing JavadocComment (please validate)

Parsing JavadocComment (please validate)
----------------------------------------

                 Key: QDOX-168
                 URL: http://jira.codehaus.org/browse/QDOX-168
             Project: QDox
          Issue Type: Improvement
          Components: Parser
    Affects Versions: 1.9.1, 1.9, 1.8
            Reporter: Robert Scholte
             Fix For: 1.10
         Attachments: javadoc-relexed.patch

Untill now the javadoc comments were read by token/word. This works for most cases, but when comments are becomming complex because of the usage of asterikses (together with tabs and spaces) the result be slightly different then the input.
I've rewritten the lexer, where the reading is based on lines instead of tokens. This makes the result much more solid, but requires some special lexing.
One testcase had 2 javadoccomments in 1 line (no sourceformatting, just one line of code). To read untill the first javadocEnd I had to use regepx inside the lexer-tokenblock.

When this patch is validated we can probably solve several open issues which refer to the usage of javadocs.
 

--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

       

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email

     [ http://jira.codehaus.org/browse/QDOX-168?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Paul Hammant closed QDOX-168.
-----------------------------

      Assignee: Robert Scholte
    Resolution: Fixed

Robert's Patch applied, some whitespace tests fixed to accommodate small changes.

> Parsing JavadocComment (please validate)
> ----------------------------------------
>
>                 Key: QDOX-168
>                 URL: http://jira.codehaus.org/browse/QDOX-168
>             Project: QDox
>          Issue Type: Improvement
>          Components: Parser
>    Affects Versions: 1.8, 1.9, 1.9.1
>            Reporter: Robert Scholte
>            Assignee: Robert Scholte
>             Fix For: 1.10
>
>         Attachments: javadoc-relexed.patch, qdox-168-fix.patch
>
>
> Untill now the javadoc comments were read by token/word. This works for most cases, but when comments are becomming complex because of the usage of asterikses (together with tabs and spaces) the result be slightly different then the input.
> I've rewritten the lexer, where the reading is based on lines instead of tokens. This makes the result much more solid, but requires some special lexing.
> One testcase had 2 javadoccomments in 1 line (no sourceformatting, just one line of code). To read untill the first javadocEnd I had to use regepx inside the lexer-tokenblock.
> When this patch is validated we can probably solve several open issues which refer to the usage of javadocs.
>  

--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

       

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email