Skip to main content

Interfaces & Namespaces

Interfaces

The complete CourierFeat-Standard public interfacesinterface areis covered by the namespaces CourierFeatStd and Courier::Platform.various subnamespaces of namespace FeatStd. All other sub namespaces ofcontaining Couriereither denoteInternal or Private in the name cover private namespaces (like Courier::Internal, Courier::DataBindingPrivate, etc.),namespaces, which are not recommended to be used in any application, as it is not guaranteed that these interfaces remain stable respectively exist in any future release. Changes in any of these private namespaces can be applied without any (prior) notifications.

Namespace CourierFeatStd

Courier discloses its functionality with the namespace Courier. This namespace comprises the following modules:

In

Namespace addition, an own Courier:FeatStd::Diagnostics namespace for error handling, logging and tracing purposes is available.

Namespace Courier:FeatStd::MemoryManagement

Namespace FeatStd::PerfMon

    MonitorPerformanceReporting

    Namespace FeatStd::Platform

    TheThis Courier::Platforminterface interfaces are also part of the public Courier interface. These interfaces definedefines the access of Courier to platform dependent objects. The implementation of this platform dependent code is not part of Courier,FeatStd, though there are a few reference platforms, like SimulationPlatform (implemented basically for Win32) or GenericPlatform (providing generic respectively stub implementations), which can used as templates for the customer.

    This platform interface can be seen as an official porting interface of CourierFeatStd to any customer specific platform setup, which is the reason for outlining it in the separate namespace Courier:FeatStd::Platform.

    Refer to module:

     

    Back to top