class apext::tsync::TsyncFvmErrorDomain

The member function [SWS_TS_14210] belongs to the class apext::tsync::TsyncFvmErrorDomain and is included via the header file apext/tsync/fvm_error_domain.h. It serves for the synchronous determination of the textual description for an occurred error code. As an input parameter, the function takes the numeric error code errorCode of type CodeType and returns the error message associated with it as a pointer to a constant string (const char *).

Regarding concurrency and fault tolerance, the specification provides comprehensive guarantees: The method is classified as thread-safe and can thus be called from concurrent threads without additional synchronization measures [SWS_TS_14210]. Furthermore, the function is classified as exception safe and marked with the specifier noexcept, whereby the throwing of exceptions during execution is precluded.

In module ts, a close relationship exists to the specification element [SWS_TS_00907]. This defines the analogous function Message for the error domain ara::tsync::TsyncErrorDomain in the header ara/tsync/tsync_error_domain.h. Both interfaces feature the same signature as well as identical guarantees regarding thread safety and exception safety, ensuring uniform querying of error texts across different domains.

The const member function Name() of class apext::tsync::TsyncFvmErrorDomain returns a pointer to an immutable string (const char*) that represents the name of the error domain for the Time-Synchronization FVM [SWS_TS_14209]. The function serves to query the identifier of the error domain at runtime. The call is executed synchronously and without parameters, and requires including the header file apext/tsync/fvm_error_domain.h [SWS_TS_14209].

Regarding error behavior, the interface is declared as noexcept and is considered exception-safe (exception safe) [SWS_TS_14209]. Since it merely references a fixed string constant, no specific error codes are returned and no error cases occur. Regarding concurrency, the method is explicitly classified as thread-safe (thread-safe) [SWS_TS_14209]. Concurrent calls from multiple threads are therefore likely to be permitted at any time without additional external synchronization or protection mechanisms. Question Q-6664ffba9d211592 (open)

In architectural interaction, the function overrides (override) the error domain identification interface and complements the analogous function from [SWS_TS_00906]. While [SWS_TS_00906] provides the name of the error domain ara::tsync::TsyncErrorDomain for basic time synchronization via ara/tsync/tsync_error_domain.h, [SWS_TS_14209] serves to identify the specialized error domain apext::tsync::TsyncFvmErrorDomain. Both methods thus follow the uniform error model of AUTOSAR Adaptive.

The member function ThrowAsException of error domain apext::tsync::TsyncFvmErrorDomain serves to synchronously throw a C++ exception based on an error code ([SWS_TS_14211]). The declaration is available via header apext/tsync/fvm_error_domain.h. The method takes the input parameter errorCode (const ara::core::ErrorCode &), instantiates a specific apext::tsync::TsyncFvmException from it, and throws it directly ([SWS_TS_14211]). Accordingly, the function specified with noexcept(false) has no return value.

For the call context, the function is specified as thread-safe (thread-safe), but designated as not exception-safe (not exception safe) ([SWS_TS_14211]). Interpretation: This classification as not exception-safe is likely attributable to the fact that throwing an exception intentionally terminates regular control flow. Question Q-4d1dbde678635320 (open) A central compiler restriction defines [SWS_CORE_10304]: If C++ exceptions are disabled in the toolchain, the function does not participate in overload resolution.

In the overall system, the function complements error handling analogously to [SWS_TS_00908] from ara::tsync::TsyncErrorDomain. While a TsyncException is thrown there, ThrowAsException in the FVM error domain enables the uniform transformation of a ara::core::ErrorCode into a C++ exception ([SWS_TS_14211]).

use

The parameterless default constructor TsyncFvmErrorDomain() synchronously creates a new instance of the error domain apext::tsync::TsyncFvmErrorDomain [SWS_TS_14208]. It expects no parameters and is declared as constexpr as well as noexcept. For inclusion, the header file apext/tsync/fvm_error_domain.h must be included [SWS_TS_14208].

Error Handling and Concurrency

Because the constructor is specified as noexcept, no exceptions occur during instantiation; execution is considered thread-safe and exception-safe [SWS_TS_14208]. The created object manages and translates error codes of the enumeration TsyncFvmErrc [SWS_TS_14202] (type alias Errc [SWS_TS_14206]), which encompasses the specific errors kFVNotAvailable and kFVInitializeFailed [SWS_TS_14202].

Interaction and Lifecycle

The domain instance provides interfaces for name and message resolution via Name() [SWS_TS_14209] and Message() [SWS_TS_14210] as well as for throwing type-specific exceptions via ThrowAsException() [SWS_TS_14211] using Exception [SWS_TS_14207]. Destruction occurs via the virtual destructor ~TsyncFvmErrorDomain() [SWS_TS_14201]. In application code, direct manual construction is likely to be rarely necessary; presumably, the global singleton instance is retrieved via GetTsyncFvmErrorDomain() [SWS_TS_14212] instead. Question Q-411a136f0129313a (open)