rspec/rules/S839/cfamily/rule.adoc

It is implementation-defined behaviour whether the reference parameter is a temporary object or a reference to the parameter. If the implementation uses a local copy (temporary object), this will be destroyed when the function returns. Any attempt to use such an object after its destruction will lead to undefined behaviour.


== Noncompliant Code Example

[source,cpp]
----
int32_t * fn1 ( int32_t & x )
{
  return &x ; // Noncompliant
}
const int32_t * fn3 ( const int32_t & x )
{
  return &x ; // Noncompliant
}
int32_t & fn4 ( int32_t & x )
{
  return x ; // Noncompliant
}
const int32_t & fn5 ( const int32_t & x )
{
  return x ; // Noncompliant
}
----


== See

* MISRA {cpp}:2008, 7-5-3


ifdef::env-github,rspecator-view[]

'''
== Implementation Specification
(visible only on this page)

include::message.adoc[]

'''
== Comments And Links
(visible only on this page)

include::comments-and-links.adoc[]
endif::env-github,rspecator-view[]