QA·C Help - 4825

	4825	Unexpected character.

Annotations

Annotations should be terminated by:

a newline, or
'*/' if the annotation is in a c-style comment, or
'//' if the annotation is to be followed by another c++-style comment.

Example:


// PRQA S 100 A1
                      // OK - a new line terminates the annoation

// PRQA S 100 A1      // OK - followed by // denoting a new C++ style comment
/* PRQA S 100 A1 */   // OK - followed by */ denoting the end of the C style comment

After QA C++ has parsed an annotation, an error will be produced if there are any tokens remaining. This ensures that QA C++ doesn't silently ignore ill-formed annotations.

Example:


// PRQA L:L1 L2 ++    // ERROR - '+' character not expected
// PRQA S Msg A1-B1   // ERROR - "A" is not expected

For the last example, the QA C++ parses the annotation as

PRQA S
Msg

. The message is therefore generated against 'A' as being the unexpected character. It is likely that an attempt was made to specify a range of locations, something that is not valid suppression syntax.

No MISRA C:2012 Rules applicable to message 4825

See also:

4810 Invalid annotation: tag 'locTag' is not defined subsequently in this file.
4811 The start of the range 'locTag', starts and ends at the same location.
4812 'tag' not allowed here.
4820 Annotation kind is expected.
4821 Colon is expected.
4822 Tag name is expected.
4823 Annotation syntax error.
4824 Invalid character in tag name.
4826 Message specification is incomplete or missing.
4827 Tag name is not allowed in the message specification of continuous suppression annotation.
4828 Invalid usage of predefined location tag.

QA·C Source Code Analyser 8.1
MISRA C:2012 Compliance Module 1.0
© 2012 Programming Research.
www.programmingresearch.com

Personality Groups | Glossary | Message Index | MISRA C:2012 Rule Index

Contents