Clang Intellisense parameter infos not working properly

Sysprogs forums Forums VisualGDB Clang Intellisense parameter infos not working properly

Viewing 2 posts - 1 through 2 (of 2 total)
  • Author
    Posts
  • #25133
    MystikReasons
    Participant

    I already opened a post for a similiar problem a while ago(https://sysprogs.com/w/forums/topic/intellisense-wrong-parameter-info/)

    One of your statement: ”
    <div class=”bbp-reply-content”>

    Hi,

    It looks like the ‘*’ frame around the comment is interfering with the comment parsing logic.

    Please ensure that the line containing the ‘@param’ comment does not have any other characters (other then spaces) in front of the @param part and VisualGDB will handle it correctly.

    These ‘*’ frames are also present in every HAL file (see screenshot #1) so the function infos aren’t being displayed when hovering over a function.

    My question: Would it be possible to update your logic so the ‘*’ frames arent interfering with your comment parsing logic?

    </div>

     

    UPDATE: Also it seems your logic for “Declared: .h file (222, 6) isn’t working properly, see screenshot #1 for the location displayed in the function info and the content at the “real” location.

    See screenshot #2 for the infos at the displayed location

    • This topic was modified 4 years, 10 months ago by MystikReasons.
    • This topic was modified 4 years, 10 months ago by MystikReasons.
    • This topic was modified 4 years, 10 months ago by MystikReasons.
    • This topic was modified 4 years, 10 months ago by MystikReasons.
    Attachments:
    You must be logged in to view attached files.
    #25142
    support
    Keymaster

    Thanks for the update. Indeed, the comment parsing for STM32 codebase would not recognize the @param tokens, however the bigger issue there is that the comments are located in the .cpp files, not .h files and hence locating them would involve a longer go-to-definition operation that is not performed when displaying comments or argument suggestions.

    We will try to improve this in one of the upcoming VisualGDB releases.

Viewing 2 posts - 1 through 2 (of 2 total)
  • You must be logged in to reply to this topic.