value_container

Aedi, a dependency injection library.

Aedi is a dependency injection library. It does provide a set of containers that do IoC, and an interface to configure application components (structs, objects, etc.)

Aim:

The aim of library is to provide a dependency injection solution that is feature rich, easy to use, easy to learn, and easy to extend up to your needs.

Having a framework that creates and wire components is quite good. In previous tutorials, was explained how to inject compile time known data, and how to reference dependent components, but while designing a framework, or a library in conjunction with AEDI framework, exposing a set of parameters might be desired. To expose a set of configuration parameters, framework provides a special version of container, that stores in those parameters, and serves them to the requestor. To use this container it should be attached to a composite container along the rest of containers, as in previous tutorial and used along them. The process of adding parameters into container is easy as with rest of shown containers, the only difference is, that register method doesn’t require an explicit component type, since it is inferred from passed value. Example below shows basic usage of value container:

1 auto container = aggregate( // Create a joint container hosting other two containers
2     singleton(), "singleton", // Create singleton container, and store it in joint container by "singleton" identity
3     prototype(), "prototype", // Create prototype container, and store it in joint container by "prototype" identity
4     values(), "parameters"  // Create value container, and store it in joint container by "prototype" identity
5 );
6 
7 with (container.configure("singleton")) {
8 
9     // ...
10 
11 }
12 
13 with (container.configure("prototype")) {
14 
15     // ...
16 }
17 
18 with (container.locate!ValueContainer("parameters").configure) {
19 
20     register(Size(200, 150, 300), "size.smarty");
21 }

As seen the configuration for value containers differs from other containers. In case of value containers configure method should know exactly what kind of configuration context to create.

Try running example. Add, modify it to understand usage of containers for already available values.

Members

Classes

Car
class Car

A class representing a car.

CarManufacturer
class CarManufacturer

A manufacturer of cars.

DieselEngine
class DieselEngine

A concrete implementation of Engine that uses diesel for propelling.

ElectricEngine
class ElectricEngine

A concrete implementation of Engine that uses electricity for propelling.

GasolineEngine
class GasolineEngine

A concrete implementation of Engine that uses gasoline for propelling.

Tire
class Tire

Tire, what it can represent else?

Interfaces

Engine
interface Engine

Interface for engines.

Structs

Color
struct Color

A struct that should be managed by container.

Size
struct Size

Size of a car.

Meta

Authors

aermicioi

License

Boost Software License - Version 1.0 - August 17th, 2003

Permission is hereby granted, free of charge, to any person or organization obtaining a copy of the software and accompanying documentation covered by this license (the "Software") to use, reproduce, display, distribute, execute, and transmit the Software, and to prepare derivative works of the Software, and to permit third-parties to whom the Software is furnished to do so, all subject to the following:

The copyright notices in the Software and this entire statement, including the above license grant, this restriction and the following disclaimer, must be included in all copies of the Software, in whole or in part, and all derivative works of the Software, unless such copies or derivative works are solely in the form of machine-executable object code generated by a source language processor.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, TITLE AND NON-INFRINGEMENT. IN NO EVENT SHALL THE COPYRIGHT HOLDERS OR ANYONE DISTRIBUTING THE SOFTWARE BE LIABLE FOR ANY DAMAGES OR OTHER LIABILITY, WHETHER IN CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.