boost-react-native-bundle

<html> <head> <meta http-equiv="Content-Type" content="text/html; charset=US-ASCII"> <title>Chapter 1. Boost.Icl</title> <link rel="stylesheet" href="../../../../doc/src/boostbook.css" type="text/css"> <meta name="generator" content="DocBook XSL Stylesheets V1.74.0"> <link rel="home" href="index.html" title="Chapter 1. Boost.Icl"> <link rel="next" href="boost_icl/examples.html" title="Examples"> </head> <body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"> <table cellpadding="2" width="100%"><tr> <td valign="top"><img alt="Boost C++ Libraries" width="277" height="86" src="../../../../boost.png"></td> <td align="center"><a href="../../../../index.html">Home</a></td> <td align="center"><a href="../../../libraries.htm">Libraries</a></td> <td align="center"><a href="http://www.boost.org/users/people.html">People</a></td> <td align="center"><a href="http://www.boost.org/users/faq.html">FAQ</a></td> <td align="center"><a href="../../../../more/index.htm">More</a></td> </tr></table> <hr> <div class="spirit-nav"><a accesskey="n" href="boost_icl/examples.html"><img src="../../../../doc/src/images/next.png" alt="Next"></a></div> <div class="chapter" lang="en"> <div class="titlepage"><div> <div><h2 class="title"> <a name="optional"></a>Chapter 1. Boost.Icl</h2></div> <div><div class="author"><h3 class="author"> Joachim Faulhaber </h3></div></div> <div>Copyright © 2007 -2010 Joachim Faulhaber</div> <div>Copyright © 1999 -2006 Cortex Software GmbH</div> <div><div class="legalnotice"> <a name="id1009066"></a> Distributed under the Boost Software License, Version 1.0. (See accompanying file LICENSE_1_0.txt or copy at <a href="http://www.boost.org/LICENSE_1_0.txt" target="_top">http://www.boost.org/LICENSE_1_0.txt</a>) </div></div> </div></div> <div class="toc"> Table of Contents <dl> <dt><a href="index.html#boost_icl.introduction">Introduction</a></dt> <dd><dl> <dt><a href="index.html#boost_icl.introduction.definition_and_basic_example">Definition and Basic Example</a></dt> <dt><a href="index.html#boost_icl.introduction.icl_s_class_templates">Icl's class templates</a></dt> <dt><a href="index.html#boost_icl.introduction.interval_combining_styles">Interval Combining Styles</a></dt> </dl></dd> <dt><a href="boost_icl/examples.html">Examples</a></dt> <dd><dl> <dt><a href="boost_icl/examples.html#boost_icl.examples.overview">Overview</a></dt> <dt><a href="boost_icl/examples/party.html">Party</a></dt> <dt><a href="boost_icl/examples/interval.html">Interval</a></dt> <dt><a href="boost_icl/examples/dynamic_interval.html">Dynamic interval</a></dt> <dt><a href="boost_icl/examples/static_interval.html">Static interval</a></dt> <dt><a href="boost_icl/examples/interval_container.html">Interval container</a></dt> <dt><a href="boost_icl/examples/overlap_counter.html">Overlap counter</a></dt> <dt><a href="boost_icl/examples/partys_height_average.html"> Party's height average</a></dt> <dt><a href="boost_icl/examples/partys_tallest_guests.html"> Party's tallest guests</a></dt> <dt><a href="boost_icl/examples/time_grids.html"> Time grids for months and weeks</a></dt> <dt><a href="boost_icl/examples/man_power.html">Man power</a></dt> <dt><a href="boost_icl/examples/user_groups.html">User groups</a></dt> <dt><a href="boost_icl/examples/std_copy.html">Std copy</a></dt> <dt><a href="boost_icl/examples/std_transform.html">Std transform</a></dt> <dt><a href="boost_icl/examples/custom_interval.html">Custom interval</a></dt> </dl></dd> <dt><a href="boost_icl/projects.html">Projects</a></dt> <dd><dl><dt><a href="boost_icl/projects.html#boost_icl.projects.large_bitset">Large Bitset</a></dt></dl></dd> <dt><a href="boost_icl/concepts.html">Concepts</a></dt> <dd><dl> <dt><a href="boost_icl/concepts.html#boost_icl.concepts.naming">Naming</a></dt> <dt><a href="boost_icl/concepts/aspects.html">Aspects</a></dt> <dt><a href="boost_icl/concepts/sets_and_maps.html">Sets and Maps</a></dt> <dt><a href="boost_icl/concepts/aggrovering.html"> Addability, Subtractability and Aggregate on Overlap</a></dt> <dt><a href="boost_icl/concepts/map_traits.html">Map Traits</a></dt> </dl></dd> <dt><a href="boost_icl/semantics.html">Semantics</a></dt> <dd><dl> <dt><a href="boost_icl/semantics.html#boost_icl.semantics.orderings_and_equivalences">Orderings and Equivalences</a></dt> <dt><a href="boost_icl/semantics/sets.html">Sets</a></dt> <dt><a href="boost_icl/semantics/maps.html">Maps</a></dt> <dt><a href="boost_icl/semantics/collectors__maps_of_sets.html">Collectors: Maps of Sets</a></dt> <dt><a href="boost_icl/semantics/quantifiers__maps_of_numbers.html">Quantifiers: Maps of Numbers</a></dt> <dt><a href="boost_icl/semantics/concept_induction.html">Concept Induction</a></dt> </dl></dd> <dt><a href="boost_icl/interface.html">Interface</a></dt> <dd><dl> <dt><a href="boost_icl/interface.html#boost_icl.interface.class_templates">Class templates</a></dt> <dt><a href="boost_icl/interface/required_concepts.html">Required Concepts</a></dt> <dt><a href="boost_icl/interface/associated_types.html">Associated Types</a></dt> <dt><a href="boost_icl/interface/function_synopsis.html">Function Synopsis</a></dt> </dl></dd> <dt><a href="boost_icl/customization.html">Customization</a></dt> <dd><dl><dt><a href="boost_icl/customization.html#boost_icl.customization.intervals">Intervals</a></dt></dl></dd> <dt><a href="boost_icl/implementation.html">Implementation</a></dt> <dd><dl> <dt><a href="boost_icl/implementation.html#boost_icl.implementation.iterative_size">Iterative size</a></dt> <dt><a href="boost_icl/implementation/complexity.html">Complexity</a></dt> <dt><a href="boost_icl/implementation/inplace_and_infix_operators.html">Inplace and infix operators</a></dt> </dl></dd> <dt><a href="boost_icl/function_reference.html">Function Reference</a></dt> <dd><dl> <dt><a href="boost_icl/function_reference.html#boost_icl.function_reference.overload_tables">Overload tables</a></dt> <dt><a href="boost_icl/function_reference/segmentational_fineness.html">Segmentational Fineness</a></dt> <dt><a href="boost_icl/function_reference/key_types.html">Key Types</a></dt> <dt><a href="boost_icl/function_reference/construct__copy__destruct.html">Construct, copy, destruct</a></dt> <dt><a href="boost_icl/function_reference/containedness.html">Containedness</a></dt> <dt><a href="boost_icl/function_reference/equivalences_and_orderings.html">Equivalences and Orderings</a></dt> <dt><a href="boost_icl/function_reference/size.html">Size</a></dt> <dt><a href="boost_icl/function_reference/range.html">Range</a></dt> <dt><a href="boost_icl/function_reference/selection.html">Selection</a></dt> <dt><a href="boost_icl/function_reference/addition.html">Addition</a></dt> <dt><a href="boost_icl/function_reference/subtraction.html">Subtraction</a></dt> <dt><a href="boost_icl/function_reference/insertion.html">Insertion</a></dt> <dt><a href="boost_icl/function_reference/erasure.html">Erasure</a></dt> <dt><a href="boost_icl/function_reference/intersection.html">Intersection</a></dt> <dt><a href="boost_icl/function_reference/symmetric_difference.html">Symmetric Difference</a></dt> <dt><a href="boost_icl/function_reference/iterator_related.html">Iterator related</a></dt> <dt><a href="boost_icl/function_reference/element_iteration.html">Element iteration</a></dt> <dt><a href="boost_icl/function_reference/streaming__conversion.html">Streaming, conversion</a></dt> <dt><a href="boost_icl/function_reference/interval_construction.html">Interval Construction</a></dt> <dt><a href="boost_icl/function_reference/additional_interval_orderings.html">Additional Interval Orderings</a></dt> <dt><a href="boost_icl/function_reference/miscellaneous_interval_functions.html">Miscellaneous Interval Functions</a></dt> </dl></dd> <dt><a href="boost_icl/acknowledgments.html">Acknowledgments</a></dt> <dt><a href="interval_container_library_reference.html">Interval Container Library Reference</a></dt> <dd><dl> <dt><a href="interval_container_library_reference.html#header.boost.icl.closed_interval_hpp">Header <boost/icl/closed_interval.hpp></a></dt> <dt><a href="header/boost/icl/continuous_interval_hpp.html">Header <boost/icl/continuous_interval.hpp></a></dt> <dt><a href="header/boost/icl/discrete_interval_hpp.html">Header <boost/icl/discrete_interval.hpp></a></dt> <dt><a href="header/boost/icl/dynamic_interval_traits_hpp.html">Header <boost/icl/dynamic_interval_traits.hpp></a></dt> <dt><a href="header/boost/icl/functors_hpp.html">Header <boost/icl/functors.hpp></a></dt> <dt><a href="header/boost/icl/gregorian_hpp.html">Header <boost/icl/gregorian.hpp></a></dt> <dt><a href="header/boost/icl/impl_config_hpp.html">Header <boost/icl/impl_config.hpp></a></dt> <dt><a href="header/boost/icl/interval_hpp.html">Header <boost/icl/interval.hpp></a></dt> <dt><a href="header/boost/icl/interval_base_map_hpp.html">Header <boost/icl/interval_base_map.hpp></a></dt> <dt><a href="header/boost/icl/interval_base_set_hpp.html">Header <boost/icl/interval_base_set.hpp></a></dt> <dt><a href="header/boost/icl/interval_bounds_hpp.html">Header <boost/icl/interval_bounds.hpp></a></dt> <dt><a href="header/boost/icl/interval_combining_style_hpp.html">Header <boost/icl/interval_combining_style.hpp></a></dt> <dt><a href="header/boost/icl/interval_map_hpp.html">Header <boost/icl/interval_map.hpp></a></dt> <dt><a href="header/boost/icl/interval_set_hpp.html">Header <boost/icl/interval_set.hpp></a></dt> <dt><a href="header/boost/icl/interval_traits_hpp.html">Header <boost/icl/interval_traits.hpp></a></dt> <dt><a href="header/boost/icl/iterator_hpp.html">Header <boost/icl/iterator.hpp></a></dt> <dt><a href="header/boost/icl/left_open_interval_hpp.html">Header <boost/icl/left_open_interval.hpp></a></dt> <dt><a href="header/boost/icl/map_hpp.html">Header <boost/icl/map.hpp></a></dt> <dt><a href="header/boost/icl/open_interval_hpp.html">Header <boost/icl/open_interval.hpp></a></dt> <dt><a href="header/boost/icl/ptime_hpp.html">Header <boost/icl/ptime.hpp></a></dt> <dt><a href="header/boost/icl/rational_hpp.html">Header <boost/icl/rational.hpp></a></dt> <dt><a href="header/boost/icl/right_open_interval_hpp.html">Header <boost/icl/right_open_interval.hpp></a></dt> <dt><a href="header/boost/icl/separate_interval_set_hpp.html">Header <boost/icl/separate_interval_set.hpp></a></dt> <dt><a href="header/boost/icl/split_interval_map_hpp.html">Header <boost/icl/split_interval_map.hpp></a></dt> <dt><a href="header/boost/icl/split_interval_set_hpp.html">Header <boost/icl/split_interval_set.hpp></a></dt> </dl></dd> </dl> </div> <div class="section boost_icl_introduction" lang="en"> <div class="titlepage"><div><div><h2 class="title" style="clear: both"> <a name="boost_icl.introduction"></a><a class="link" href="index.html#boost_icl.introduction" title="Introduction">Introduction</a> </h2></div></div></div> <div class="toc"><dl> <dt><a href="index.html#boost_icl.introduction.definition_and_basic_example">Definition and Basic Example</a></dt> <dt><a href="index.html#boost_icl.introduction.icl_s_class_templates">Icl's class templates</a></dt> <dt><a href="index.html#boost_icl.introduction.interval_combining_styles">Interval Combining Styles</a></dt> </dl></div> “A bug crawls across the boost docs on my laptop screen. Let him be! We need all the readers we can get.” -- Freely adapted from <a href="http://en.wikipedia.org/wiki/Jack_Kornfield" target="_top">Jack Kornfield</a> Intervals are almost ubiquitous in software development. Yet they are very easily coded into user defined classes by a pair of numbers so they are only implicitly used most of the time. The meaning of an interval is simple. They represent all the elements between their lower and upper bound and thus a set. But unlike sets, intervals usually can not be added to a single new interval. If you want to add intervals to a collection of intervals that does still represent a set, you arrive at the idea of interval_sets provided by this library. Interval containers of the ICL have been developed initially at <a href="http://www.cortex-software.de/desktopdefault.aspx" target="_top">Cortex Software GmbH</a> to solve problems related to date and time interval computations in the context of a Hospital Information System. Time intervals with associated values like amount of invoice or set of therapies had to be manipulated in statistics, billing programs and therapy scheduling programs. So the ICL emerged out of those industrial use cases. It extracts generic code that helps to solve common problems from the date and time problem domain and can be beneficial in other fields as well. One of the most advantageous aspects of interval containers is their very compact representation of sets and maps. Working with sets and maps of elements can be very inefficient, if in a given problem domain, elements are typically occurring in contiguous chunks. Besides a compact representation of associative containers, that can reduce the cost of space and time drastically, the ICL comes with a universal mechanism of aggregation, that allows to combine associated values in meaningful ways when intervals overlap on insertion. For a condensed introduction and overview you may want to look at the <a href="http://www.herold-faulhaber.de/boost_icl/doc/libs/icl/doc/boostcon09/intro_to_itl.pdf" target="_top">presentation material on the ICL from BoostCon2009</a>. <div class="section boost_icl_introduction_definition_and_basic_example" lang="en"> <div class="titlepage"><div><div><h3 class="title"> <a name="boost_icl.introduction.definition_and_basic_example"></a><a class="link" href="index.html#boost_icl.introduction.definition_and_basic_example" title="Definition and Basic Example">Definition and Basic Example</a> </h3></div></div></div> The Interval Container Library (ICL) provides <code class="computeroutput"><a class="link" href="boost/icl/interval.html" title="Struct template interval">intervals</a></code> and two kinds of interval containers: <code class="computeroutput"><a class="link" href="boost/icl/interval_set.html" title="Class template interval_set">interval_sets</a></code> and <code class="computeroutput"><a class="link" href="boost/icl/interval_map.html" title="Class template interval_map">interval_maps</a></code>. <div class="itemizedlist"><ul type="disc"> <li> An <code class="computeroutput"><a class="link" href="boost/icl/interval_base_set.html" title="Class template interval_base_set">interval_set</a></code> is a set that is implemented as a set of intervals. </li> <li> An <code class="computeroutput"><a class="link" href="boost/icl/interval_base_map.html" title="Class template interval_base_map">interval_map</a></code> is a map that is implemented as a map of interval value pairs. </li> </ul></div> <a name="boost_icl.introduction.definition_and_basic_example.two_aspects"></a><h5> <a name="id1009249"></a> <a class="link" href="index.html#boost_icl.introduction.definition_and_basic_example.two_aspects">Two Aspects</a> </h5> <code class="computeroutput"><a class="link" href="boost/icl/interval_base_set.html" title="Class template interval_base_set">Interval_sets</a></code> and <code class="computeroutput"><a class="link" href="boost/icl/interval_base_map.html" title="Class template interval_base_map">interval_maps</a></code> expose two different aspects in their interfaces: (1) The functionality of a set or a map, which is the more abstract aspect. And (2) the functionality of a container of intervals which is the more specific and implementation related aspect. In practice both aspects are useful and are therefore supported. The first aspect, that will be called fundamental aspect, is the more important one. It means that we can use an <code class="computeroutput"><a class="link" href="boost/icl/interval_set.html" title="Class template interval_set">interval_set</a></code> or <code class="computeroutput"><a class="link" href="boost/icl/interval_map.html" title="Class template interval_map">interval_map</a></code> like a set or map of elements. It exposes the same functions. <pre class="programlisting">interval_set<int> mySet; mySet.insert(42); bool has_answer = contains(mySet, 42); </pre> The second aspect, that will be called segmental aspect, allows to exploit the fact, that the elements of <code class="computeroutput"><a class="link" href="boost/icl/interval_set.html" title="Class template interval_set">interval_sets</a></code> and <code class="computeroutput"><a class="link" href="boost/icl/interval_map.html" title="Class template interval_map">interval_maps</a></code> are clustered in intervals or segments that we can iterate over. <pre class="programlisting">// Switch on my favorite telecasts using an interval_set interval<seconds>::type news(make_seconds("20:00:00"), make_seconds("20:15:00")); interval<seconds>::type talk_show(make_seconds("22:45:30"), make_seconds("23:30:50")); interval_set<seconds> myTvProgram; myTvProgram.add(news).add(talk_show); // Iterating over elements (seconds) would be silly ... for(interval_set<seconds>::iterator telecast = myTvProgram.begin(); telecast != myTvProgram.end(); ++telecast) //...so this iterates over intervals TV.switch_on(*telecast); </pre> Working with <code class="computeroutput"><a class="link" href="boost/icl/interval_base_set.html" title="Class template interval_base_set">interval_sets</a></code> and <code class="computeroutput"><a class="link" href="boost/icl/interval_base_map.html" title="Class template interval_base_map">interval_maps</a></code> can be beneficial whenever the elements of sets appear in contiguous chunks: <code class="computeroutput"><a class="link" href="boost/icl/interval.html" title="Struct template interval">intervals</a></code>. This is obviously the case in many problem domains, particularly in fields that deal with computations related to date and time. <a name="boost_icl.introduction.definition_and_basic_example.addabitlity_and_subtractability"></a><h5> <a name="id1017462"></a> <a class="link" href="index.html#boost_icl.introduction.definition_and_basic_example.addabitlity_and_subtractability">Addabitlity and Subtractability</a> </h5> Unlike <code class="computeroutput">std::sets</code> and <code class="computeroutput">maps</code>, <code class="computeroutput"><a class="link" href="boost/icl/interval_base_set.html" title="Class template interval_base_set">interval_sets</a></code> and <code class="computeroutput"><a class="link" href="boost/icl/interval_base_map.html" title="Class template interval_base_map">interval_maps</a></code> implement concept <code class="computeroutput">Addable</code> and <code class="computeroutput">Subtractable</code>. So <code class="computeroutput"><a class="link" href="boost/icl/interval_base_set.html" title="Class template interval_base_set">interval_sets</a></code> define an <code class="computeroutput">operator +=</code> that is naturally implemented as set union and an <code class="computeroutput">operator -=</code> that is consequently implemented as set difference. In the Icl <code class="computeroutput"><a class="link" href="boost/icl/interval_base_map.html" title="Class template interval_base_map">interval_maps</a></code> are addable and subtractable as well. It turned out to be a very fruitful concept to propagate the addition or subtraction to the <code class="computeroutput"><a class="link" href="boost/icl/interval_base_map.html" title="Class template interval_base_map">interval_map's</a></code> associated values in cases where the insertion of an interval value pair into an <code class="computeroutput"><a class="link" href="boost/icl/interval_map.html" title="Class template interval_map">interval_map</a></code> resulted in a collision of the inserted interval value pair with interval value pairs, that are already in the <code class="computeroutput"><a class="link" href="boost/icl/interval_map.html" title="Class template interval_map">interval_map</a></code>. This operation propagation is called aggregate on overlap. <a name="boost_icl.introduction.definition_and_basic_example.aggregate_on_overlap"></a><h5> <a name="id1017612"></a> <a class="link" href="index.html#boost_icl.introduction.definition_and_basic_example.aggregate_on_overlap">Aggregate on Overlap</a> </h5> This is a first motivating example of a very small party, demonstrating the aggregate on overlap principle on <code class="computeroutput"><a class="link" href="boost/icl/interval_map.html" title="Class template interval_map">interval_maps</a></code>: In the example Mary enters the party first. She attends during the time interval <code class="computeroutput">[20:00,22:00)</code>. Harry enters later. He stays within <code class="computeroutput">[21:00,23:00)</code>. <pre class="programlisting">typedef std::set<string> guests; interval_map<time, guests> party; party += make_pair(interval<time>::right_open(time("20:00"), time("22:00")), guests("Mary")); party += make_pair(interval<time>::right_open(time("21:00"), time("23:00")), guests("Harry")); // party now contains [20:00, 21:00)->{"Mary"} [21:00, 22:00)->{"Harry","Mary"} //guest sets aggregated on overlap [22:00, 23:00)->{"Harry"} </pre> On overlap of intervals, the corresponding name sets are accumulated. At the points of overlap the intervals are split. The accumulation of content on overlap of intervals is done via an <code class="computeroutput">operator +=</code> that has to be implemented for the associated values of the <code class="computeroutput"><a class="link" href="boost/icl/interval_map.html" title="Class template interval_map">interval_map</a></code>. In the example the associated values are <code class="computeroutput">guest sets</code>. Thus a <code class="computeroutput">guest set</code> has to implement <code class="computeroutput">operator +=</code> as set union. As can be seen from the example an <code class="computeroutput"><a class="link" href="boost/icl/interval_map.html" title="Class template interval_map">interval_map</a></code> has both a decompositional behavior (on the time dimension) as well as an accumulative one (on the associated values). Addability and aggregate on overlap are useful features on <code class="computeroutput"><a class="link" href="boost/icl/interval_map.html" title="Class template interval_map">interval_maps</a></code> implemented via function <code class="computeroutput">add</code> and <code class="computeroutput">operator +=</code>. But you can also use them with the traditional <a class="link" href="boost_icl/function_reference/insertion.html" title="Insertion">insert semantics</a> that behaves like <code class="computeroutput">std::map::insert</code> generalized for interval insertion. </div> <div class="section boost_icl_introduction_icl_s_class_templates" lang="en"> <div class="titlepage"><div><div><h3 class="title"> <a name="boost_icl.introduction.icl_s_class_templates"></a><a class="link" href="index.html#boost_icl.introduction.icl_s_class_templates" title="Icl's class templates">Icl's class templates</a> </h3></div></div></div> In addition to interval containers we can work with containers of elements that are behavioral equal to the interval containers: On the fundamental aspect they have exactly the same functionality. An <a href="http://www.cplusplus.com/reference/stl/set/" target="_top"><code class="computeroutput">std::set</code> </a> of the STL is such an equivalent set implementation. Due to the aggregation facilities of the icl's interval maps <a href="http://www.cplusplus.com/reference/stl/set/" target="_top"><code class="computeroutput">std::map</code> </a> is fundamentally not completely equivalent to an <code class="computeroutput"><a class="link" href="boost/icl/interval_map.html" title="Class template interval_map">interval_map</a></code>. Therefore there is an extra <code class="computeroutput"><a class="link" href="boost/icl/map.html" title="Class template map">icl::map</a></code> class template for maps of elements in the icl. <div class="itemizedlist"><ul type="disc"> <li> The <a href="http://www.cplusplus.com/reference/stl/set/" target="_top"><code class="computeroutput">std::set</code> </a> is behavioral equal to <code class="computeroutput"><a class="link" href="boost/icl/interval_base_set.html" title="Class template interval_base_set">interval_sets</a></code> on the fundamental aspect. </li> <li> An <code class="computeroutput"><a class="link" href="boost/icl/map.html" title="Class template map">icl::map</a></code> is behavioral equal to <code class="computeroutput"><a class="link" href="boost/icl/interval_base_map.html" title="Class template interval_base_map">interval_maps</a></code> on the fundamental aspect. Specifically an <code class="computeroutput"><a class="link" href="boost/icl/map.html" title="Class template map">icl::map</a></code> implements aggregate on overlap, which is named aggregate on collision for an element container. </li> </ul></div> The following tables give an overview over the main class templates provided by the icl. <div class="table"> <a name="id1018421"></a>Table 1.1. Interval class templates <div class="table-contents"><table class="table" summary="Interval class templates"> <colgroup> <col> <col> <col> </colgroup> <thead><tr> <th> group </th> <th> form </th> <th> template </th> </tr></thead> <tbody> <tr> <td> statically bounded </td> <td> asymmetric </td> <td> <code class="computeroutput"><a class="link" href="boost/icl/right_open_interval.html" title="Class template right_open_interval">right_open_interval</a></code> </td> </tr> <tr> <td> </td> <td> </td> <td> <code class="computeroutput"><a class="link" href="boost/icl/left_open_interval.html" title="Class template left_open_interval">left_open_interval</a></code> </td> </tr> <tr> <td> </td> <td> symmetric </td> <td> <code class="computeroutput"><a class="link" href="boost/icl/closed_interval.html" title="Class template closed_interval">closed_interval</a></code> </td> </tr> <tr> <td> </td> <td> </td> <td> <code class="computeroutput"><a class="link" href="boost/icl/open_interval.html" title="Class template open_interval">open_interval</a></code> </td> </tr> <tr> <td> dynamically bounded </td> <td> </td> <td> <code class="computeroutput"><a class="link" href="boost/icl/discrete_interval.html" title="Class template discrete_interval">discrete_interval</a></code> </td> </tr> <tr> <td> </td> <td> </td> <td> <code class="computeroutput"><a class="link" href="boost/icl/continuous_interval.html" title="Class template continuous_interval">continuous_interval</a></code> </td> </tr> </tbody> </table></div> </div> Statically bounded intervals always have the same kind of interval borders, e.g. right open borders<code class="computeroutput">[a..b)</code> for <code class="computeroutput"><a class="link" href="boost/icl/right_open_interval.html" title="Class template right_open_interval">right_open_interval</a></code>. Dynamically bounded intervals can have different borders. Refer to the chapter about <a class="link" href="boost_icl/interface.html#boost_icl.interface.class_templates.intervals" title="Intervals">intervals</a> for details. <div class="table"> <a name="id1018685"></a>Table 1.2. Container class templates <div class="table-contents"><table class="table" summary="Container class templates"> <colgroup> <col> <col> <col> <col> </colgroup> <thead><tr> <th> granularity </th> <th> style </th> <th> sets </th> <th> maps </th> </tr></thead> <tbody> <tr> <td> interval </td> <td> joining </td> <td> <code class="computeroutput"><a class="link" href="boost/icl/interval_set.html" title="Class template interval_set">interval_set</a></code> </td> <td> <code class="computeroutput"><a class="link" href="boost/icl/interval_map.html" title="Class template interval_map">interval_map</a></code> </td> </tr> <tr> <td> </td> <td> separating </td> <td> <code class="computeroutput"><a class="link" href="boost/icl/separate_interval_set.html" title="Class template separate_interval_set">separate_interval_set</a></code> </td> <td> </td> </tr> <tr> <td> </td> <td> splitting </td> <td> <code class="computeroutput"><a class="link" href="boost/icl/split_interval_set.html" title="Class template split_interval_set">split_interval_set</a></code> </td> <td> <code class="computeroutput"><a class="link" href="boost/icl/split_interval_map.html" title="Class template split_interval_map">split_interval_map</a></code> </td> </tr> <tr> <td> element </td> <td> </td> <td> (<a href="http://www.cplusplus.com/reference/stl/set/" target="_top"><code class="computeroutput">std::set</code> </a>) </td> <td> <code class="computeroutput"><a class="link" href="boost/icl/map.html" title="Class template map">map</a></code> </td> </tr> </tbody> </table></div> </div> <a href="http://www.cplusplus.com/reference/stl/set/" target="_top"><code class="computeroutput">Std::set</code> </a> is placed in paretheses, because it is not a class template of the ICL. It can be used as element container though that is behavioral equal to the ICL's interval sets on their fundamental aspect. Column style refers to the different ways in which interval containers combine added intervals. These combining styles are described in the next section. </div> <div class="section boost_icl_introduction_interval_combining_styles" lang="en"> <div class="titlepage"><div><div><h3 class="title"> <a name="boost_icl.introduction.interval_combining_styles"></a><a class="link" href="index.html#boost_icl.introduction.interval_combining_styles" title="Interval Combining Styles">Interval Combining Styles</a> </h3></div></div></div> When we add intervals or interval value pairs to interval containers, the intervals can be added in different ways: Intervals can be joined or split or kept separate. The different interval combining styles are shown by example in the tables below. <div class="table"> <a name="id1018963"></a>Table 1.3. Interval container's ways to combine intervals <div class="table-contents"><table class="table" summary="Interval container's ways to combine intervals"> <colgroup> <col> <col> <col> <col> </colgroup> <thead><tr> <th> </th> <th> joining </th> <th> separating </th> <th> splitting </th> </tr></thead> <tbody> <tr> <td> set </td> <td> <code class="computeroutput"><a class="link" href="boost/icl/interval_set.html" title="Class template interval_set">interval_set</a></code> </td> <td> <code class="computeroutput"><a class="link" href="boost/icl/separate_interval_set.html" title="Class template separate_interval_set">separate_interval_set</a></code> </td> <td> <code class="computeroutput"><a class="link" href="boost/icl/split_inter