Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Clarification for 7-3-1: extern "C++"
#1
For headers included by other C and C++ headers it is vital to use extern "C++".
But the rule implicitly forbids it by only allowing 3 kind of top level declarations.

Is it really intended to use this as the only compliant way:
Code:
extern "C"
{
  extern "C++"
  {
    namespace MY_API
    {
    }
  }
}
<t></t>
Reply
#2
I have to disagree, 7-3-1 is not the problem here, 16-2-1 is (see http://www.misra.org.uk/forum/viewtopic....1549#p3031)
Typically, in mixed C/C++ applications, you require extern "C" in the C Header only, because the C Module is compiled with a C Compiler and the C++ Module with a C++ Compiler.
If the C Header is checked with MISRA C++ (because the C++ module is), you break 16-2-1 (illustration below).

legacy.h
Code:
#ifndef LEGACY_H
#define LEGACY_H

#ifdef __cplusplus// MISRA C 2012 compliant, but non-compliant with MISRA C++ 16-2-1
extern "C" {// compliant with MISRA C++ 7-3-1
#endif

void foo(void);

#ifdef __cplusplus// MISRA C 2012 compliant, but non-compliant with MISRA C++ 16-2-1
}
#endif

#endif
legacy.c
Code:
#include "legacy.h"
/* no extern "C" required*/
void foo(void)
{
}
main.cpp
Code:
#include "legacy.h"// compliant, no extern "C" required either

int main(void)
{
  foo();
  return 0;
}

I think MISRA has not put much thought into mixed C/C++ scenarios.
<t></t>
Reply
#3
The preferred solution is as suggested by dg1980, with a deviation for the 16-2-1 violation
Posted by and on behalf of
the MISRA C++ Working Group
Reply


Forum Jump:


Users browsing this thread: 1 Guest(s)