Repository navigation
Use standard file:line: level: message format - #711
Merged
Merged
Conversation
Contributor
|
+1. Howl also supports this format. |
o11c
force-pushed
the
standard-error-format
branch
from
June 13, 2015 06:18
ea979d1 to
654d63b
Compare
Contributor
Author
|
Patch is a little more complex now that I'm dealing with the unit tests. Not unit test framework I'm familiar with. |
This gives better tool integration.
o11c
force-pushed
the
standard-error-format
branch
from
June 15, 2015 04:26
654d63b to
7c0125c
Compare
Contributor
Author
|
@JukkaL This PR is particularly prone to getting outdated. |
Contributor
Author
|
@JukkaL ping? Not having this merged makes it significantly harder to write future patches reliably. |
Collaborator
|
Thanks for implementing this, and sorry for the delay! It's a good idea to move towards a more standard format for messages. We should still continue improving the messages by including column numbers and showing the actual source code lines containing errors. |
JukkaL
added a commit
that referenced
this pull request
Jun 23, 2015
Use standard `file:line: level: message` format
|
Thank you @JukkaL for merging this. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
There is a standard format for errors and warnings. Using it means better integration for other tools.
filemust be absolute or relative to the current working directory.lineis 1-based and any line without it is not considered for the protocol.colis 1-based may be omitted. It should probably always be omitted if something like C's#fileis used to replace the file/line that the compiler sees with the file/line of the program that emitted that source file.levelmay beerrororwarningto receive special handling in editors, or anything else (commonlynotefor multi-location errors/warnings) or omitted to not be collected specially. Essentially this is part ofmessagein those cases.[-option]is the command-line argument used to enable a warning, and may be omitted. This is essentially part ofmessagefor all programmatic purposes, but useful for humans.Programs such as gcc and make produce this format; IDEs and text editors such as vim and kate consume it. There are doubtless uncountably many more programs that also use the same protocol.