• Locked Locked
  • Replies 1 reply
  • Subscribers 53 subscribers
  • Views 374 views
  • Users 0 members are here
Support feedback
Options
Options
Related

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

Format change of compiler diagnostics

Cody Addison
Expert 4540 points

We are considering changing the format of diagnostics reported by the compiler tools. This change is in an effort to standardize all diagnostic messages generated by the tools. Currently, the shell reports diagnostics with either a prefix of ERROR or >>ERROR, depending on the context. Other tools use just the all CAPS ERROR:, and the linker uses error: for its prefix. We are planning on changing to the format used by the linker. The diagnostics generated during parsing will not be affected.

I would like to get any feedback regarding this change. Our biggest concern is that we will break some user's process because they are parsing our diagnostic messages. While we are concerned about these issues, we believe that having a consistent diagnostic format will result in a better user experience moving forward.

 

Regards,

Cody Addison

  • Genius 4077 points

    I would appreciate a consistent error format - it should be possible to adapt the error parsers in the user tools.

    But a consistent format should only be a starting point. I know many other tools that have a configurable output format.

    So a consistent default output format plus a configurable output format would really be nice!