Menu

Optionally parsing a userAttribute "USER_ATTRIBUTE" in declaration and Optionally parsing type_qualifier an type specifier before cast expression in the assignment_expression

2023-11-20
2023-11-20
  • Hariharan Mari

    Hariharan Mari - 2023-11-20

    Previously the Moritz tool could not parse when we have user specific attribute in the declaration eg. static int array[10] USER_ATTRIBUTE; (Here USER_ATTRIBUTE is a Macro) will now be able to parse.
    Similary in code MACRO(const int variable = 0); is not parsed before and now it can be parsed.

     
  • Eckard Klotz

    Eckard Klotz - 2023-11-20

    Hello Hariharan Mari.

    To be honest I don't understand your comment.

    Previously the Moritz tool could not parse ... ... and now it can be parsed.

    Do you have now an issue or not?

    Your description suggests that you break the syntax-rules in the source by using preprocessor defines.

    • Since the parser has no own preprocessor, it tries to analyse the source as it is.
    • The reason for this is the fact that Moritz should document the source and not the resulting binary.
    • This may result in a parser-termination if the source-code itself is not following the usual C/Cpp Syntax by using the preprocessor definition.

    If you still have an issue, please provide a small example to reproduce it.

    • Based on this example I will try to find a solution.
    • However the missing preprocessor will be a limitation that could not be solved.

    Best regards,
    Eckard Klotz.

     

Log in to post a comment.

Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.