def Error(filename, linenum, category, confidence, message):
if _ShouldPrintError(category, confidence, linenum):<EOL><INDENT>_cpplint_state.IncrementErrorCount(category)<EOL>if _cpplint_state.output_format == '<STR_LIT>':<EOL><INDENT>_cpplint_state.PrintError('<STR_LIT>' % (<EOL>filename, linenum, message, category, confidence))<EOL><DEDENT>elif _cpplint_state.output_format == '<STR_LIT>':<EOL><INDENT>sys.stderr.write('<STR_LIT>' % (<EOL>filename, linenum, message, category, confidence))<EOL><DEDENT>elif _cpplint_state.output_format == '<STR_LIT>':<EOL><INDENT>_cpplint_state.AddJUnitFailure(filename, linenum, message, category,<EOL>confidence)<EOL><DEDENT>else:<EOL><INDENT>final_message = '<STR_LIT>' % (<EOL>filename, linenum, message, category, confidence)<EOL>sys.stderr.write(final_message)<EOL><DEDENT><DEDENT>
Logs the fact we've found a lint error.

    We log where the error was found, and also our confidence in the error,
    that is, how certain we are this is a legitimate style regression, and
    not a misidentification or a use that's sometimes justified.

    False positives can be suppressed by the use of
    "cpplint(category)"  comments on the offending line.  These are
    parsed into _error_suppressions.

    Args:
      filename: The name of the file containing the error.
      linenum: The number of the line containing the error.
      category: A string used to describe the "category" this bug
        falls under: "whitespace", say, or "runtime".  Categories
        may have a hierarchy separated by slashes: "whitespace/indent".
      confidence: A number from 1-5 representing a confidence score for
        the error, with 5 meaning that we are certain of the problem,
        and 1 meaning that it could be a legitimate construct.
      message: The error message.