Part I. The Boost C++ LibrariesLibraries Listed AlphabeticallyLibraries Listed by CategoryString and text processingContainersIteratorsAlgorithmsFunction objects and higher-order programmingGeneric programmingTemplate metaprogrammingPreprocessor metaprogrammingConcurrent programmingMath and numericsCorrectness and testingData structuresInput/OutputInter-language supportMemoryParsingMiscellaneousBroken compiler workaroundsBoost.AnyIntroductionExamplesReferenceValueType requirementsHeader <boost/any.hpp>Class bad_any_castClass anyFunction any_castAcknowledgementsBoost.ArrayIntroductionReferenceHeader <boost/array.hpp>Class template arrayDesign RationaleFor more information...AcknowledgementsConcept referenceConceptsConcept AssignableConcept InputIteratorConcept OutputIteratorConcept ForwardIteratorConcept BidirectionalIteratorConcept RandomAccessIteratorConcept DefaultConstructibleConcept CopyConstructibleConcept EqualityComparableConcept LessThanComparableConcept SignedIntegerBoost.Date_TimeConceptualMotivationDomain ConceptsDesign ConceptsMore InformationGregorianDate ClassDate Duration (aka Days)Date PeriodDate IteratorsDate Generators/AlgorithmsGregorian CalendarClass day_clockPosix TimePtime ClassTime DurationTime PeriodTime IteratorsLocal Time AdjustmentDetailsCalculationsDesign GoalsTradeoffs: Stability, Predictability, and ApproximationsSerializationTerminologyReferencesBuild-Compiler InformationTestsChange HistoryAcknowledgementsExamplesGeneral Usage ExamplesDates as StringsDays AliveDays Between New YearsEnd of the MonthsLocalization DemonstrationDate Period CalculationsPrint HolidaysPrint MonthMonth AddingTime MathPrint HoursLocal to UTC ConversionTime PeriodsLibrary ReferenceDate Time ReferenceHeader <boost/date_time/adjust_functors.hpp>Class template day_functorClass template month_functorClass template week_functorClass template year_functorHeader <boost/date_time/c_local_time_adjustor.hpp>Class template c_local_adjustorHeader <boost/date_time/c_time.hpp>Header <boost/date_time/compiler_config.hpp>Header <boost/date_time/constrained_value.hpp>Class template constrained_valueClass template simple_exception_policyHeader <boost/date_time/date.hpp>Class template dateHeader <boost/date_time/date_clock_device.hpp>Class template day_clockHeader <boost/date_time/date_defs.hpp>Header <boost/date_time/date_duration.hpp>Class template date_durationStruct duration_traits_longStruct duration_traits_adaptedHeader <boost/date_time/date_duration_types.hpp>Class template weeks_durationClass template months_durationClass template years_durationHeader <boost/date_time/date_format_simple.hpp>Class template simple_formatClass simple_format<wchar_t>Header <boost/date_time/date_formatting.hpp>Class template month_formatterClass template ymd_formatterClass template date_formatterHeader <boost/date_time/date_formatting_limited.hpp>Header <boost/date_time/date_formatting_locales.hpp>Class template ostream_month_formatterClass template ostream_weekday_formatterClass template ostream_ymd_formatterClass template ostream_date_formatterHeader <boost/date_time/date_generators.hpp>Class template year_based_generatorClass template partial_dateClass template nth_kday_of_monthClass template first_kday_of_monthClass template last_kday_of_monthClass template first_kday_afterClass template first_kday_beforeFunction template days_until_weekdayFunction template days_before_weekdayFunction template next_weekdayFunction template previous_weekdayHeader <boost/date_time/date_iterator.hpp>Class template date_itr_baseClass template date_itrHeader <boost/date_time/date_names_put.hpp>Class template date_names_putClass template all_date_names_putHeader <boost/date_time/dst_rules.hpp>Class template dst_calculatorClass template dst_calc_engineClass template us_dst_rulesClass template null_dst_rulesHeader <boost/date_time/dst_transition_generators.hpp>Class template dst_day_calc_ruleClass template day_calc_dst_ruleHeader <boost/date_time/filetime_functions.hpp>Function template time_from_ftimeHeader <boost/date_time/gregorian_calendar.hpp>Class template gregorian_calendar_baseHeader <boost/date_time/int_adapter.hpp>Class template int_adapterFunction template operator<<Header <boost/date_time/iso_format.hpp>Class template iso_format_baseClass iso_format_base<wchar_t>Class template iso_formatClass template iso_extended_formatHeader <boost/date_time/local_time_adjustor.hpp>Class template utc_adjustmentClass template dynamic_local_time_adjustorClass template static_local_time_adjustorClass template local_adjustorHeader <boost/date_time/local_timezone_defs.hpp>Struct template us_dst_traitStruct template eu_dst_traitStruct template uk_dst_traitStruct template acst_dst_traitHeader <boost/date_time/microsec_time_clock.hpp>Class template microsec_clockHeader <boost/date_time/parse_format_base.hpp>Type ymd_order_specHeader <boost/date_time/period.hpp>Class template periodHeader <boost/date_time/special_defs.hpp>Header <boost/date_time/time.hpp>Class template base_timeHeader <boost/date_time/time_clock.hpp>Class template second_clockHeader <boost/date_time/time_defs.hpp>Header <boost/date_time/time_duration.hpp>Class template time_durationClass template subsecond_durationHeader <boost/date_time/time_formatting_streams.hpp>Class template ostream_time_duration_formatterClass template ostream_time_formatterClass template ostream_time_period_formatterHeader <boost/date_time/time_iterator.hpp>Class template time_itrHeader <boost/date_time/time_parsing.hpp>Function template parse_delimited_time_durationHeader <boost/date_time/time_resolution_traits.hpp>Struct time_resolution_traits_bi32_implStruct time_resolution_traits_adapted32_implStruct time_resolution_traits_bi64_implStruct time_resolution_traits_adapted64_implClass template time_resolution_traitsHeader <boost/date_time/time_system_counted.hpp>Struct template counted_time_repClass template counted_time_systemHeader <boost/date_time/time_system_split.hpp>Class template split_timedate_systemHeader <boost/date_time/wrapping_int.hpp>Class template wrapping_intClass template wrapping_int2Header <boost/date_time/year_month_day.hpp>Struct template year_month_day_baseGregorian ReferenceHeader <boost/date_time/gregorian/formatters.hpp>Header <boost/date_time/gregorian/formatters_limited.hpp>Header <boost/date_time/gregorian/greg_calendar.hpp>Class gregorian_calendarHeader <boost/date_time/gregorian/greg_date.hpp>Class dateHeader <boost/date_time/gregorian/greg_day.hpp>Struct bad_day_of_monthClass greg_dayHeader <boost/date_time/gregorian/greg_day_of_year.hpp>Struct bad_day_of_yearHeader <boost/date_time/gregorian/greg_duration.hpp>Header <boost/date_time/gregorian/greg_duration_types.hpp>Struct greg_durations_configHeader <boost/date_time/gregorian/greg_facet.hpp>Struct greg_facet_configFunction template operator<<Function template operator<<Function template operator<<Function template operator<<Header <boost/date_time/gregorian/greg_month.hpp>Struct bad_monthClass greg_monthHeader <boost/date_time/gregorian/greg_weekday.hpp>Struct bad_weekdayClass greg_weekdayHeader <boost/date_time/gregorian/greg_year.hpp>Struct bad_yearClass greg_yearHeader <boost/date_time/gregorian/greg_ymd.hpp>Header <boost/date_time/gregorian/gregorian.hpp>Header <boost/date_time/gregorian/gregorian_types.hpp>Header <boost/date_time/gregorian/parsers.hpp>Posix Time ReferenceHeader <boost/date_time/posix_time/conversion.hpp>Function template from_ftimeHeader <boost/date_time/posix_time/date_duration_operators.hpp>Function operator+Function operator+=Function operator-Function operator-=Function operator+Function operator+=Function operator-Function operator-=Header <boost/date_time/posix_time/posix_time.hpp>Header <boost/date_time/posix_time/posix_time_config.hpp>Class time_durationStruct simple_time_repClass posix_time_system_configClass millisec_posix_time_system_configHeader <boost/date_time/posix_time/posix_time_duration.hpp>Class hoursClass minutesClass secondsHeader <boost/date_time/posix_time/posix_time_system.hpp>Header <boost/date_time/posix_time/posix_time_types.hpp>Header <boost/date_time/posix_time/ptime.hpp>Class ptimeHeader <boost/date_time/posix_time/time_formatters.hpp>Function template operator>>Header <boost/date_time/posix_time/time_formatters_limited.hpp>Header <boost/date_time/posix_time/time_parsers.hpp>Function duration_from_stringHeader <boost/date_time/posix_time/time_period.hpp>Boost.FunctionIntroductionHistory & Compatibility NotesTutorialBasic UsageFree functionsMember functionsReferences to Function ObjectsComparing Boost.Function function objectsReferenceDefinitionsHeader <boost/function.hpp>Class bad_function_callClass function_baseClass template functionNClass template functionHeader <boost/function_equal.hpp>Function template function_equalFrequently Asked QuestionsMiscellaneous NotesBoost.Function vs. Function PointersPerformanceFunction object wrapper sizeCopying efficiencyInvocation efficiencyCombatting virtual function "bloat"AcknowledgementsTestsuiteAcceptance testsNegative testsBoost.LambdaIn a nutshellGetting StartedInstalling the libraryConventions used in this documentIntroductionMotivationIntroduction to lambda expressionsPartial function applicationTerminologyUsing the libraryIntroductory ExamplesParameter and return types of lambda functorsAbout actual arguments to lambda functorsStoring bound arguments in lambda functionsLambda expressions in detailsPlaceholdersOperator expressionsOperators that cannot be overloadedAssignment and subscript operatorsLogical operatorsComma operatorFunction call operatorMember pointer operatorBind expressionsFunction pointers or references as targetsMember functions as targetsMember variables as targetsFunction objects as targetsOverriding the deduced return typeNullary lambda functors and retDelaying constants and variablesLambda expressions for control structuresSwitch statementExceptionsConstruction and destructionSpecial lambda expressionsPreventing argument substitutionUnlambdaProtectRvalues as actual arguments to lambda functorsCasts, sizeof and typeidCast expressionsSizeof and typeidNesting STL algorithm invocationsExtending return type deduction systemPractical considerationsPerformanceAbout compilingPortabilityTest coverageRelation to other Boost librariesBoost FunctionBoost BindFirst argument of bind expressionContributorsAppendix A. Rationale for some of the design decisionsLambda functor arityBibliographyBoost.Program_optionsIntroductionTutorialGetting StartedOption DetailsMultiple SourcesLibrary OverviewOptions Description ComponentSyntactic informationSemantic informationPositional optionsParsers ComponentStorage ComponentAnnotated List of SymbolsHow ToNon-conventional SyntaxResponse FilesWinmain Command LineOption Groups and Hidden OptionsCustom ValidatorsUnicode SupportDesign DiscussionUnicode SupportAcknowledgementsReferenceHeader <boost/program_options/cmdline.hpp>Type style_tHeader <boost/program_options/environment_iterator.hpp>Class environment_iteratorHeader <boost/program_options/eof_iterator.hpp>Class template eof_iteratorHeader <boost/program_options/errors.hpp>Class errorClass invalid_syntaxClass unknown_optionClass ambiguous_optionClass multiple_valuesClass multiple_occurrencesClass validation_errorClass invalid_option_valueClass too_many_positional_options_errorClass too_few_positional_options_errorClass invalid_command_line_syntaxClass invalid_command_line_styleHeader <boost/program_options/option.hpp>Class template basic_optionHeader <boost/program_options/options_description.hpp>Class option_descriptionClass options_description_easy_initClass options_descriptionClass duplicate_option_errorHeader <boost/program_options/parsers.hpp>Class template basic_parsed_optionsClass basic_parsed_options<wchar_t>Class common_command_line_parserClass template basic_command_line_parserFunction template parse_command_lineFunction template parse_config_fileFunction parse_environmentFunction parse_environmentHeader <boost/program_options/positional_options.hpp>Class positional_options_descriptionHeader <boost/program_options/value_semantic.hpp>Class value_semanticClass template value_semantic_codecvt_helperClass value_semantic_codecvt_helper<char>Class value_semantic_codecvt_helper<wchar_t>Class untyped_valueClass template typed_valueFunction valueFunction wvalueFunction bool_switchHeader <boost/program_options/variables_map.hpp>Class variable_valueClass abstract_variables_mapClass variables_mapFunction storeFunction storeFunction notifyHeader <boost/program_options/version.hpp>Macro BOOST_PROGRAM_OPTIONS_VERSIONBoost.RefIntroductionReferenceHeader <boost/ref.hpp>Class template reference_wrapperClass template is_reference_wrapperClass template unwrap_referenceAcknowledgementsBoost.SignalsIntroductionTutorialHow to Read this TutorialCompatibility NoteHello, World! (Beginner)Calling multiple slotsConnecting multiple slots (Beginner)Ordering slot call groups (Intermediate)Passing values to and from slotsSlot Arguments (Beginner)Signal Return Values (Advanced)Connection ManagementDisconnecting Slots (Beginner)Scoped connections (Intermediate)Disconnecting equivalent slots (Intermediate)Automatic connection management (Intermediate)When can disconnections occur? (Intermediate)Passing slots (Intermediate)Linking against the Signals libraryReferenceHeader <boost/signal.hpp>Class template signalNClass template signalHeader <boost/signals/slot.hpp>Class template slotHeader <boost/signals/trackable.hpp>Class trackableHeader <boost/signals/connection.hpp>Class connectionClass scoped_connectionHeader <boost/visit_each.hpp>Function template visit_eachHeader <boost/last_value.hpp>Class template last_valueClass last_value<void>Frequently Asked QuestionsDesign OverviewType Erasureconnection classSlot Call Iteratorvisit_each function templateDesign RationaleChoice of Slot DefinitionsUser-level Connection ManagementCombiner InterfaceConnection Interfaces: += operatortrackable rationaletrackable copying behaviorWhy derivation from trackable?Comparison with other Signal/Slot implementationslibsigc++.NET delegatesTestsuiteAcceptance testsBoost String Algorithms LibraryIntroductionUsageFirst ExampleCase conversionPredicates and ClassificationTrimmingFind algorithmsReplace AlgorithmsFind IteratorSplitQuick ReferenceAlgorithmsFinders and FormattersIteratorsClassificationDesign TopicsString Representationiterator_range classCollection TraitsSequence TraitsFind AlgorithmsReplace AlgorithmsFind Iterators & Split AlgorithmsException SafetyConceptsDefinitionsFinder ConceptFormatter conceptReferenceHeader <boost/algorithm/string/case_conv.hpp>Function to_lower_copyFunction template to_lowerFunction to_upper_copyFunction template to_upperHeader <boost/algorithm/string/classification.hpp>Function is_classifiedFunction is_spaceFunction is_alnumFunction is_alphaFunction is_cntrlFunction is_digitFunction is_graphFunction is_lowerFunction is_printFunction is_punctFunction is_upperFunction is_xdigitFunction template is_any_ofFunction template is_from_rangeFunction template operator&&Function template operator||Function template operator!Header <boost/algorithm/string/collection_traits.hpp>Struct template collection_traitsStruct template value_type_ofStruct template difference_type_ofStruct template iterator_ofStruct template const_iterator_ofStruct template result_iterator_ofFunction template sizeFunction template emptyFunction beginFunction endHeader <boost/algorithm/string/compare.hpp>Struct is_equalStruct is_iequalHeader <boost/algorithm/string/concept.hpp>Struct template FinderConceptStruct template FormatterConceptHeader <boost/algorithm/string/constants.hpp>Type token_compress_mode_typeHeader <boost/algorithm/string/erase.hpp>Function erase_range_copyFunction template erase_rangeFunction erase_first_copyFunction template erase_firstFunction ierase_first_copyFunction template ierase_firstFunction erase_last_copyFunction template erase_lastFunction ierase_last_copyFunction template ierase_lastFunction erase_nth_copyFunction template erase_nthFunction ierase_nth_copyFunction template ierase_nthFunction erase_all_copyFunction template erase_allFunction ierase_all_copyFunction template ierase_allFunction erase_head_copyFunction template erase_headFunction erase_tail_copyFunction template erase_tailHeader <boost/algorithm/string/find.hpp>Function template findFunction template find_firstFunction template ifind_firstFunction template find_lastFunction template ifind_lastFunction template find_nthFunction template ifind_nthFunction template find_headFunction template find_tailFunction template find_tokenHeader <boost/algorithm/string/find_format.hpp>Function find_format_copyFunction template find_formatFunction find_format_all_copyFunction template find_format_allFunction template regex_finderFunction template regex_formatterHeader <boost/algorithm/string/find_iterator.hpp>Class template find_iteratorClass template split_iteratorFunction template make_find_iteratorFunction template make_split_iteratorHeader <boost/algorithm/string/finder.hpp>Function first_finderFunction last_finderFunction nth_finderFunction head_finderFunction tail_finderFunction template token_finderFunction range_finderHeader <boost/algorithm/string/formatter.hpp>Function template const_formatterFunction template identity_formatterFunction template empty_formatterHeader <boost/algorithm/string/iterator_range.hpp>Class template iterator_rangeFunction template operator<<Function template make_iterator_rangeFunction template make_iterator_rangeFunction template copy_iterator_rangeFunction template transform_iterator_rangeHeader <boost/algorithm/string/predicate.hpp>Function starts_withFunction template istarts_withFunction ends_withFunction template iends_withFunction containsFunction template icontainsFunction equalsFunction template iequalsFunction template allHeader <boost/algorithm/string/regex.hpp>Function template find_regexFunction replace_regex_copyFunction template replace_regexFunction replace_all_regex_copyFunction template replace_all_regexFunction erase_regex_copyFunction template erase_regexFunction erase_all_regex_copyFunction template erase_all_regexFunction template find_all_regexFunction template split_regexHeader <boost/algorithm/string/regex_find_format.hpp>Function template regex_finderFunction template regex_formatterHeader <boost/algorithm/string/replace.hpp>Function replace_range_copyFunction template replace_rangeFunction replace_first_copyFunction template replace_firstFunction ireplace_first_copyFunction template ireplace_firstFunction replace_last_copyFunction template replace_lastFunction ireplace_last_copyFunction template ireplace_lastFunction replace_nth_copyFunction template replace_nthFunction ireplace_nth_copyFunction template ireplace_nthFunction replace_all_copyFunction template replace_allFunction ireplace_all_copyFunction template ireplace_allFunction replace_head_copyFunction template replace_headFunction replace_tail_copyFunction template replace_tailHeader <boost/algorithm/string/sequence_traits.hpp>Class template has_native_replaceClass template has_stable_iteratorsClass template has_const_time_insertClass template has_const_time_eraseHeader <boost/algorithm/string/split.hpp>Function template find_allFunction template ifind_allFunction template splitHeader <boost/algorithm/string/std_containers_traits.hpp>Header <boost/algorithm/string.hpp>Header <boost/algorithm/string_regex.hpp>Header <boost/algorithm/string/trim.hpp>Function trim_left_copy_ifFunction template trim_left_copyFunction template trim_left_ifFunction template trim_leftFunction trim_right_copy_ifFunction template trim_right_copyFunction template trim_right_ifFunction template trim_rightFunction trim_copy_ifFunction template trim_copyFunction template trim_ifFunction template trimRationaleLocalesRegular ExpressionsEnvironmentBuildExamplesTestsPortabilityCreditsAcknowledgmentsBoost.ThreadsOverviewIntroductionDangersGeneral considerationsTesting and debugging considerationsGetting a head startC++ Standard Library usage in multithreaded programsRuntime librariesPotentially non-thread-safe functionsCommon guarantees for all Boost.Threads componentsExceptionsNonCopyable requirementDesignGoalsIterative PhasesPhase 1, Synchronization PrimitivesPhase 2, Thread Management and Thread Specific StorageThe Next PhaseConceptsMutexesLocking StrategiesRecursive Locking StrategyChecked Locking StrategyUnchecked Locking StrategyUnspecified Locking StrategyScheduling PoliciesFIFO Scheduling PolicyPriority Driven PolicyUnspecified PolicyMutex ConceptsMutex ConceptTryMutex ConceptTimedMutex ConceptMutex ModelsLock ConceptsLock ConceptScopedLock ConceptTryLock ConceptScopedTryLock ConceptTimedLock ConceptScopedTimedLock ConceptLock ModelsRead/Write MutexesLocking StrategiesRecursive Locking StrategyChecked Locking StrategyUnchecked Locking StrategyUnspecified Locking StrategyThread IdentificationLock PromotionLock DemotionScheduling PoliciesInter-Class Scheduling PoliciesReaderPriorityWriterPriorityAlternatingPriority/ManyReadsAlternatingPriority/SingleReadIntra-Class Scheduling PoliciesMutex ConceptsReadWriteMutex ConceptTryReadWriteMutex ConceptTimedReadWriteMutex ConceptMutex ModelsLock ConceptsReadWriteLock ConceptScopedReadWriteLock ConceptTryReadWriteLock ExpressionsScopedTryReadWriteLock ExpressionsTimedReadWriteLock ConceptScopedTimedReadWriteLock ConceptLock ModelsRationaleRationale for the Creation of Boost.ThreadsRationale for the Low Level Primitives Supported in Boost.ThreadsRationale for the Lock DesignRationale for NonCopyable Thread Type1. Use case: Simple creation of a thread.2. Use case: Creation of a thread that's later joined.3. Use case: Simple creation of several threads in a loop.4. Use case: Creation of several threads in a loop which are later joined.5. Use case: Creation of a thread whose ownership is passed to another object/method.6. Use case: Creation of a thread whose ownership is shared between multiple objects.1. Comparison: simple creation of a thread.2. Comparison: creation of a thread that's later joined.3. Comparison: simple creation of several threads in a loop.4. Comparison: creation of several threads in a loop which are later joined.5. Comparison: creation of a thread whose ownership is passed to another object/method.6. Comparison: creation of a thread whose ownership is shared between multiple objects.Rationale for not providing Event VariablesReferenceHeader <boost/thread/barrier.hpp>Class barrierHeader <boost/thread/condition.hpp>Class conditionHeader <boost/thread/exceptions.hpp>Class lock_errorClass thread_resource_errorHeader <boost/thread/mutex.hpp>Class mutexClass try_mutexClass timed_mutexHeader <boost/thread/once.hpp>Macro BOOST_ONCE_INITFunction call_onceHeader <boost/thread/recursive_mutex.hpp>Class recursive_mutexClass recursive_try_mutexClass recursive_timed_mutexHeader <boost/thread/read_write_mutex.hpp>Type read_write_scheduling_policyClass read_write_mutexClass try_read_write_mutexClass timed_read_write_mutexHeader <boost/thread/thread.hpp>Class threadClass thread_groupHeader <boost/thread/tss.hpp>Class thread_specific_ptrHeader <boost/thread/xtime.hpp>Type xtime_clock_typesStruct xtimeFrequently Asked QuestionsConfigurationLibrary Defined Public MacrosLibrary Defined Implementation MacrosBuildBuilding the Boost.Threads LibrariesTesting the Boost.Threads LibrariesImplementation NotesWin32Release NotesBoost 1.32.0Documentation converted to BoostBookStatically-link build option addedBarrier functionality addedRead/write mutex functionality addedThread-specific pointer functionality changedMutex implementation changed for Win32Windows CE support improvedGlossaryAcknowledgementsAcknowledgementsBibliographyBoost.TriboolIntroductionTutorialBasic usageRenaming the indeterminate statetribool input/outputReferenceHeader <boost/logic/tribool.hpp>Class triboolFunction indeterminateFunction operator!Function operator&&Function operator||Function operator==Function operator!=Macro BOOST_TRIBOOL_THIRD_STATEHeader <boost/logic/tribool_fwd.hpp>Header <boost/logic/tribool_io.hpp>Class template indeterminate_nameFunction template get_default_indeterminate_nameFunction template operator<<Function template operator>>TestsuiteAcceptance testsBoost.VariantIntroductionAbstractMotivationProblemSolution: A Motivating ExampleTutorialBasic UsageAdvanced TopicsPreprocessor macrosUsing a type sequence to specify bounded typesRecursive variant typesRecursive types with recursive_wrapperRecursive types with make_recursive_variantBinary visitationReferenceConceptsBoundedTypeStaticVisitorExamplesOutputStreamableHeader <boost/variant.hpp>Header <boost/variant/variant_fwd.hpp>Macro BOOST_VARIANT_LIMIT_TYPESMacro BOOST_VARIANT_ENUM_PARAMSMacro BOOST_VARIANT_ENUM_SHIFTED_PARAMSMacro BOOST_VARIANT_NO_REFERENCE_SUPPORTMacro BOOST_VARIANT_NO_TYPE_SEQUENCE_SUPPORTMacro BOOST_VARIANT_NO_FULL_RECURSIVE_VARIANT_SUPPORTHeader <boost/variant/variant.hpp>Class template variantFunction template swapFunction template operator<<Class template make_variant_overHeader <boost/variant/recursive_variant.hpp>Class template make_recursive_variantClass template make_recursive_variant_overHeader <boost/variant/recursive_wrapper.hpp>Class template recursive_wrapperClass template is_recursive_wrapperClass template unwrap_recursive_wrapperHeader <boost/variant/apply_visitor.hpp>Class template apply_visitor_delayed_tFunction apply_visitorHeader <boost/variant/get.hpp>Class bad_getFunction getHeader <boost/variant/bad_visit.hpp>Class bad_visitHeader <boost/variant/static_visitor.hpp>Class template static_visitorHeader <boost/variant/visitor_ptr.hpp>Class template visitor_ptr_tFunction template visitor_ptrDesign Overview"Never-Empty" GuaranteeThe GuaranteeThe Implementation ProblemThe "Ideal" Solution: False HopesAn Initial Solution: Double StorageCurrent Approach: Temporary Heap BackupEnabling OptimizationsFuture Direction: Policy-based ImplementationMiscellaneous NotesBoost.Variant vs. Boost.AnyPortabilityTroubleshooting"Template instantiation depth exceeds maximum"GNU GCC"Internal heap limit reached"Microsoft Visual C++AcknowledgmentsReferencesPart II. The BoostBook Documentation FormatIntroductionGetting StartedConfiguring local DocBook XSL and DTD distributionsConfiguring Apache FOP for PostScript/PDF OutputConfiguring Doxygen for Documentation ExtractionTroubleshootingDocumenting librariesDefining a BoostBook libraryFrom HTML to BoostBookSectioning in BoostBookBringing Together a BoostBook DocumentLinking in BoostBookReferenceBoostBook element class-specializationBoostBook element link-testBoostBook element link-fail-testBoostBook element typedefBoostBook element static-constantBoostBook element codeBoostBook element destructorBoostBook element template-type-parameterBoostBook element descriptionBoostBook element librarylistBoostBook element library-referenceBoostBook element boostbookBoostBook element unionBoostBook element inheritBoostBook element template-varargsBoostBook element sourceBoostBook element functionBoostBook element postconditionsBoostBook element compile-testBoostBook element methodBoostBook element snippetBoostBook element constructorBoostBook element namespaceBoostBook element if-failsBoostBook element free-function-groupBoostBook element functionnameBoostBook element librarycategoryBoostBook element notesBoostBook element data-memberBoostBook element specializationBoostBook element union-specializationBoostBook element throwsBoostBook element template-argBoostBook element method-groupBoostBook element requirementBoostBook element preconditionBoostBook element paramtypeBoostBook element using-classBoostBook element run-testBoostBook element librarypurposeBoostBook element copy-assignmentBoostBook element run-fail-testBoostBook element templateBoostBook element compile-fail-testBoostBook element returnsBoostBook element defaultBoostBook element parameterBoostBook element signatureBoostBook element overloaded-functionBoostBook element classBoostBook element librarycategorydefBoostBook element typeBoostBook element enumvalueBoostBook element overloaded-methodBoostBook element programlistingBoostBook element complexityBoostBook element purposeBoostBook element template-nontype-parameterBoostBook element libraryBoostBook element librarycategorylistBoostBook element using-namespaceBoostBook element struct-specializationBoostBook element structBoostBook element libBoostBook element enumBoostBook element requiresBoostBook element effectsBoostBook element librarynameBoostBook element libraryinfoBoostBook element testsuiteBoostBook element headerBoostBook element rationalePart III. Boost.Build v2 User ManualHow to use this documentInstallationTutorialHello, worldPropertiesBuild Requests and Target RequirementsProject AttributesProject HierarchiesLibraries and Dependent TargetsLibrary dependenciesStatic and shared libariesConditions and alternativesPrebuilt targetsUser documentationConfigurationWriting JamfilesOverviewMain targetsProjectsAdditional Jamfile rulesProject rootBuild processBuild requestBuilding a main targetBuilding a projectBuiltin target typesProgramsLibrariesAliasInstallingTestingBuiltin featuresDifferences to Boost.Build V1ConfigurationWriting JamfilesBuild processExtender ManualIntroductionTarget typesScannersTools and generatorsFeaturesMain target rulesToolset modulesDetailed referenceGeneral informationInitializationCommand lineCommand line argumentsCommand line optionsWriting JamfilesGenerated headersBuild processAlternative selectionDetermining common propertiesFeatures and propertiesProperty ValidityFeature AttributesFeature DeclarationBuild VariantsProperty refinementConditional propertiesTarget identifiers and referencesGeneratorsSelecting and ranking viable generatorsRunning generatorsSelecting dependency graphProperty adjustmentTransformations cacheFrequently Asked QuestionsI'm getting "Duplicate name of actual target" error. What does it mean?Accessing environment variablesHow to control properties order?How to control the library order on Unix?Can I get output of external program as a variable in a Jamfile?How to get the project-root location?How to change compilation flags for one file?Why are the dll-path and hardcode-dll-paths properties useful?Targets in site-config.jamAppendix B. Boost.Build v2 architectureOverviewThe build layerThe tools layerTargetsDependency scanningSupport for different scanning algorithmsAbility to scan the same file several timesProper detection of dependencies on generated files.Proper detection of dependencies from generated filesFile targetsTypesTarget pathsThe Boost C++ LibrariesThe Boost C++ LibrariesThe Boost C++ LibrariesThe Boost C++ LibrariesTable of ContentsI. The Boost C++ Libraries Boost.Any Introduction Examples Reference ValueType requirements Header <boost/any.hpp> Acknowledgements Boost.Array Introduction Reference Header <boost/array.hpp> Design Rationale For more information... Acknowledgements Boost.Date_Time Conceptual Motivation Domain Concepts Design Concepts More Information Gregorian Date Class Date Duration (aka Days) Date Period Date Iterators Date Generators/Algorithms Gregorian Calendar Class day_clock Posix Time Ptime Class Time Duration Time Period Time Iterators Local Time Adjustment Details Calculations Design Goals Tradeoffs: Stability, Predictability, and Approximations Serialization Terminology References Build-Compiler Information Tests Change History Acknowledgements Examples General Usage Examples Dates as Strings Days Alive Days Between New Years End of the Months Localization Demonstration Date Period Calculations Print Holidays Print Month Month Adding Time Math Print Hours Local to UTC Conversion Time Periods Library Reference Date Time Reference Gregorian Reference Posix Time Reference Boost.Function Introduction History & Compatibility Notes Tutorial Basic Usage Free functions Member functions References to Function Objects Comparing Boost.Function function objects Reference Definitions Header <boost/function.hpp> Header <boost/function_equal.hpp> Frequently Asked Questions Miscellaneous Notes Boost.Function vs. Function Pointers Performance Combatting virtual function "bloat" Acknowledgements Testsuite Acceptance tests Negative tests Boost.Lambda In a nutshell Getting Started Installing the library Conventions used in this document Introduction Motivation Introduction to lambda expressions Using the library Introductory Examples Parameter and return types of lambda functors About actual arguments to lambda functors Storing bound arguments in lambda functions Lambda expressions in details Placeholders Operator expressions Bind expressions Overriding the deduced return type Delaying constants and variables Lambda expressions for control structures Exceptions Construction and destruction Special lambda expressions Casts, sizeof and typeid Nesting STL algorithm invocations Extending return type deduction system Practical considerations Performance About compiling Portability Relation to other Boost libraries Boost Function Boost Bind Contributors Boost.Program_options Introduction Tutorial Getting Started Option Details Multiple Sources Library Overview Options Description Component Parsers Component Storage Component Annotated List of Symbols How To Non-conventional Syntax Response Files Winmain Command Line Option Groups and Hidden Options Custom Validators Unicode Support Design Discussion Unicode Support Acknowledgements Reference Header <boost/program_options/cmdline.hpp> Header <boost/program_options/environment_iterator.hpp> Header <boost/program_options/eof_iterator.hpp> Header <boost/program_options/errors.hpp> Header <boost/program_options/option.hpp> Header <boost/program_options/options_description.hpp> Header <boost/program_options/parsers.hpp> Header <boost/program_options/positional_options.hpp> Header <boost/program_options/value_semantic.hpp> Header <boost/program_options/variables_map.hpp> Header <boost/program_options/version.hpp> Boost.Ref Introduction Reference Header <boost/ref.hpp> Acknowledgements Boost.Signals Introduction Tutorial How to Read this Tutorial Compatibility Note Hello, World! (Beginner) Calling multiple slots Passing values to and from slots Connection Management Linking against the Signals library Reference Header <boost/signal.hpp> Header <boost/signals/slot.hpp> Header <boost/signals/trackable.hpp> Header <boost/signals/connection.hpp> Header <boost/visit_each.hpp> Header <boost/last_value.hpp> Frequently Asked Questions Design Overview Type Erasure connection class Slot Call Iterator visit_each function template Design Rationale Choice of Slot Definitions User-level Connection Management Combiner Interface Connection Interfaces: += operator trackable rationale Comparison with other Signal/Slot implementations Testsuite Acceptance tests Boost String Algorithms Library Introduction Usage First Example Case conversion Predicates and Classification Trimming Find algorithms Replace Algorithms Find Iterator Split Quick Reference Algorithms Finders and Formatters Iterators Classification Design Topics String Representation iterator_range class Collection Traits Sequence Traits Find Algorithms Replace Algorithms Find Iterators & Split Algorithms Exception Safety Concepts Definitions Finder Concept Formatter concept Reference Header <boost/algorithm/string/case_conv.hpp> Header <boost/algorithm/string/classification.hpp> Header <boost/algorithm/string/collection_traits.hpp> Header <boost/algorithm/string/compare.hpp> Header <boost/algorithm/string/concept.hpp> Header <boost/algorithm/string/constants.hpp> Header <boost/algorithm/string/erase.hpp> Header <boost/algorithm/string/find.hpp> Header <boost/algorithm/string/find_format.hpp> Header <boost/algorithm/string/find_iterator.hpp> Header <boost/algorithm/string/finder.hpp> Header <boost/algorithm/string/formatter.hpp> Header <boost/algorithm/string/iterator_range.hpp> Header <boost/algorithm/string/predicate.hpp> Header <boost/algorithm/string/regex.hpp> Header <boost/algorithm/string/regex_find_format.hpp> Header <boost/algorithm/string/replace.hpp> Header <boost/algorithm/string/sequence_traits.hpp> Header <boost/algorithm/string/split.hpp> Header <boost/algorithm/string/std_containers_traits.hpp> Header <boost/algorithm/string.hpp> Header <boost/algorithm/string_regex.hpp> Header <boost/algorithm/string/trim.hpp> Rationale Locales Regular Expressions Environment Build Examples Tests Portability Credits Acknowledgments Boost.Threads Overview Introduction Dangers C++ Standard Library usage in multithreaded programs Common guarantees for all Boost.Threads components Design Goals Iterative Phases Phase 1, Synchronization Primitives Phase 2, Thread Management and Thread Specific Storage The Next Phase Concepts Mutexes Read/Write Mutexes Rationale Rationale for the Creation of Boost.Threads Rationale for the Low Level Primitives Supported in Boost.Threads Rationale for the Lock Design Rationale for NonCopyable Thread Type Rationale for not providing Event Variables Reference Header <boost/thread/barrier.hpp> Header <boost/thread/condition.hpp> Header <boost/thread/exceptions.hpp> Header <boost/thread/mutex.hpp> Header <boost/thread/once.hpp> Header <boost/thread/recursive_mutex.hpp> Header <boost/thread/read_write_mutex.hpp> Header <boost/thread/thread.hpp> Header <boost/thread/tss.hpp> Header <boost/thread/xtime.hpp> Frequently Asked Questions Configuration Library Defined Public Macros Library Defined Implementation Macros Build Building the Boost.Threads Libraries Testing the Boost.Threads Libraries Implementation Notes Win32 Release Notes Boost 1.32.0 Acknowledgements Boost.Tribool Introduction Tutorial Basic usage Renaming the indeterminate state tribool input/output Reference Header <boost/logic/tribool.hpp> Header <boost/logic/tribool_fwd.hpp> Header <boost/logic/tribool_io.hpp> Testsuite Acceptance tests Boost.Variant Introduction Abstract Motivation Tutorial Basic Usage Advanced Topics Reference Concepts Header <boost/variant.hpp> Header <boost/variant/variant_fwd.hpp> Header <boost/variant/variant.hpp> Header <boost/variant/recursive_variant.hpp> Header <boost/variant/recursive_wrapper.hpp> Header <boost/variant/apply_visitor.hpp> Header <boost/variant/get.hpp> Header <boost/variant/bad_visit.hpp> Header <boost/variant/static_visitor.hpp> Header <boost/variant/visitor_ptr.hpp> Design Overview "Never-Empty" Guarantee Miscellaneous Notes Boost.Variant vs. Boost.Any Portability Troubleshooting Acknowledgments References II. The BoostBook Documentation Format Introduction Getting Started Configuring local DocBook XSL and DTD distributions Configuring Apache FOP for PostScript/PDF Output Configuring Doxygen for Documentation Extraction Troubleshooting Documenting libraries Defining a BoostBook library From HTML to BoostBook Sectioning in BoostBook Bringing Together a BoostBook Document Linking in BoostBook Reference
BoostBook element class-specialization
BoostBook element link-test
BoostBook element link-fail-test
BoostBook element typedef
BoostBook element static-constant
BoostBook element code
BoostBook element destructor
BoostBook element template-type-parameter
BoostBook element description
BoostBook element librarylist
BoostBook element library-reference
BoostBook element boostbook
BoostBook element union
BoostBook element inherit
BoostBook element template-varargs
BoostBook element source
BoostBook element function
BoostBook element postconditions
BoostBook element compile-test
BoostBook element method
BoostBook element snippet
BoostBook element constructor
BoostBook element namespace
BoostBook element if-fails
BoostBook element free-function-group
BoostBook element functionname
BoostBook element librarycategory
BoostBook element notes
BoostBook element data-member
BoostBook element specialization
BoostBook element union-specialization
BoostBook element throws
BoostBook element template-arg
BoostBook element method-group
BoostBook element requirement
BoostBook element precondition
BoostBook element paramtype
BoostBook element using-class
BoostBook element run-test
BoostBook element librarypurpose
BoostBook element copy-assignment
BoostBook element run-fail-test
BoostBook element template
BoostBook element compile-fail-test
BoostBook element returns
BoostBook element default
BoostBook element parameter
BoostBook element signature
BoostBook element overloaded-function
BoostBook element class
BoostBook element librarycategorydef
BoostBook element type
BoostBook element enumvalue
BoostBook element overloaded-method
BoostBook element programlisting
BoostBook element complexity
BoostBook element purpose
BoostBook element template-nontype-parameter
BoostBook element library
BoostBook element librarycategorylist
BoostBook element using-namespace
BoostBook element struct-specialization
BoostBook element struct
BoostBook element lib
BoostBook element enum
BoostBook element requires
BoostBook element effects
BoostBook element libraryname
BoostBook element libraryinfo
BoostBook element testsuite
BoostBook element header
BoostBook element rationale III. Boost.Build v2 User Manual How to use this document Installation Tutorial Hello, world Properties Build Requests and Target Requirements Project Attributes Project Hierarchies Libraries and Dependent Targets Library dependencies Static and shared libaries Conditions and alternatives Prebuilt targets User documentation Configuration Writing Jamfiles Overview Main targets Projects Additional Jamfile rules Project root Build process Build request Building a main target Building a project Builtin target types Programs Libraries Alias Installing Testing Builtin features Differences to Boost.Build V1 Configuration Writing Jamfiles Build process Extender Manual Introduction Target types Scanners Tools and generators Features Main target rules Toolset modules Detailed reference General information Initialization Command line Writing Jamfiles Generated headers Build process Alternative selection Determining common properties Features and properties Build Variants Property refinement Conditional properties Target identifiers and references Generators Selecting and ranking viable generators Running generators Selecting dependency graph Property adjustment Transformations cache Frequently Asked Questions
I'm getting "Duplicate name of actual target" error. What
does it mean?
Accessing environment variables
How to control properties order?
How to control the library order on Unix?
Can I get output of external program as a variable in a Jamfile?
How to get the project-root location?
How to change compilation flags for one file?
Why are the dll-path and
hardcode-dll-paths properties useful?
Targets in site-config.jam B. Boost.Build v2 architecture Overview The build layer The tools layer Targets Dependency scanning The Boost C++ LibrariesThe Boost C++ LibrariesList of Tables1. Construction and destruction related function objects. 2. Action types 3. Test 1CPU time of expressions with integer multiplication written as a lambda expression and as a traditional hand-coded function object class.
The running times are expressed in arbitrary units. 4. Test 2CPU time of arithmetic expressions written as lambda
expressions, as classic STL unnamed functions (using compose2, bind1st etc.) and as traditional hand-coded function object classes.
Using BLL terminology,
a and b are bound arguments in the expressions, and x is open.
All variables were of types double.
The running times are expressed in arbitrary units. 1. Case Conversion 2. Trimming 3. Predicates 4. Find algorithms 5. Erase/Replace 6. Split 7. Finders 8. Formatters 9. Find Iterators 10. Predicates 11. Collection Traits 12. Sequence Traits 13. Notation 14. Valid Expressions 15. Valid Expressions 1. Mutex Expressions 2. TryMutex Expressions 3. TimedMutex Expressions 4. Mutex Models 5. Lock Expressions 6. ScopedLock Expressions 7. TryLock Expressions 8. ScopedTryLock Expressions 9. TimedLock Expressions 10. ScopedTimedLock Expressions 11. Lock Models 12. ReadWriteMutex Expressions 13. TryReadWriteMutex Expressions 14. TimedReadWriteMutex Expressions 15. Mutex Models 16. ReadWriteLock Expressions 17. ScopedReadWriteLock Expressions 18. TryReadWriteLock Expressions 19. ScopedTryReadWriteLock Expressions 20. TimedReadWriteLock Expressions 21. ScopedTimedReadWriteLock Expressions 22. Lock Models 23. Supported Lock Types 24. Supported Lock Types 25. Supported Lock Types 26. Thread States 27. Thread States Transitions 28. Memory Visibility 1. BoostBook Output Formats 1. Converting HTML elements to BoostBook 1. 2. 1. Search paths for configuration files 2. Command line options The Boost C++ LibrariesThe Boost C++ LibrariesList of Examples1. Throwing and handling exceptions in lambda expressions. 1. A Skeletal BoostBook Library Part I. The Boost C++ LibrariesThe Boost C++ LibrariesThe Boost C++ LibrariesTable of ContentsBoost.Any Introduction Examples Reference ValueType requirements Header <boost/any.hpp> Acknowledgements Boost.Array Introduction Reference Header <boost/array.hpp> Design Rationale For more information... Acknowledgements Boost.Date_Time Conceptual Motivation Domain Concepts Design Concepts More Information Gregorian Date Class Date Duration (aka Days) Date Period Date Iterators Date Generators/Algorithms Gregorian Calendar Class day_clock Posix Time Ptime Class Time Duration Time Period Time Iterators Local Time Adjustment Details Calculations Design Goals Tradeoffs: Stability, Predictability, and Approximations Serialization Terminology References Build-Compiler Information Tests Change History Acknowledgements Examples General Usage Examples Dates as Strings Days Alive Days Between New Years End of the Months Localization Demonstration Date Period Calculations Print Holidays Print Month Month Adding Time Math Print Hours Local to UTC Conversion Time Periods Library Reference Date Time Reference Gregorian Reference Posix Time Reference Boost.Function Introduction History & Compatibility Notes Tutorial Basic Usage Free functions Member functions References to Function Objects Comparing Boost.Function function objects Reference Definitions Header <boost/function.hpp> Header <boost/function_equal.hpp> Frequently Asked Questions Miscellaneous Notes Boost.Function vs. Function Pointers Performance Combatting virtual function "bloat" Acknowledgements Testsuite Acceptance tests Negative tests Boost.Lambda In a nutshell Getting Started Installing the library Conventions used in this document Introduction Motivation Introduction to lambda expressions Using the library Introductory Examples Parameter and return types of lambda functors About actual arguments to lambda functors Storing bound arguments in lambda functions Lambda expressions in details Placeholders Operator expressions Bind expressions Overriding the deduced return type Delaying constants and variables Lambda expressions for control structures Exceptions Construction and destruction Special lambda expressions Casts, sizeof and typeid Nesting STL algorithm invocations Extending return type deduction system Practical considerations Performance About compiling Portability Relation to other Boost libraries Boost Function Boost Bind Contributors Boost.Program_options Introduction Tutorial Getting Started Option Details Multiple Sources Library Overview Options Description Component Parsers Component Storage Component Annotated List of Symbols How To Non-conventional Syntax Response Files Winmain Command Line Option Groups and Hidden Options Custom Validators Unicode Support Design Discussion Unicode Support Acknowledgements Reference Header <boost/program_options/cmdline.hpp> Header <boost/program_options/environment_iterator.hpp> Header <boost/program_options/eof_iterator.hpp> Header <boost/program_options/errors.hpp> Header <boost/program_options/option.hpp> Header <boost/program_options/options_description.hpp> Header <boost/program_options/parsers.hpp> Header <boost/program_options/positional_options.hpp> Header <boost/program_options/value_semantic.hpp> Header <boost/program_options/variables_map.hpp> Header <boost/program_options/version.hpp> Boost.Ref Introduction Reference Header <boost/ref.hpp> Acknowledgements Boost.Signals Introduction Tutorial How to Read this Tutorial Compatibility Note Hello, World! (Beginner) Calling multiple slots Passing values to and from slots Connection Management Linking against the Signals library Reference Header <boost/signal.hpp> Header <boost/signals/slot.hpp> Header <boost/signals/trackable.hpp> Header <boost/signals/connection.hpp> Header <boost/visit_each.hpp> Header <boost/last_value.hpp> Frequently Asked Questions Design Overview Type Erasure connection class Slot Call Iterator visit_each function template Design Rationale Choice of Slot Definitions User-level Connection Management Combiner Interface Connection Interfaces: += operator trackable rationale Comparison with other Signal/Slot implementations Testsuite Acceptance tests Boost String Algorithms Library Introduction Usage First Example Case conversion Predicates and Classification Trimming Find algorithms Replace Algorithms Find Iterator Split Quick Reference Algorithms Finders and Formatters Iterators Classification Design Topics String Representation iterator_range class Collection Traits Sequence Traits Find Algorithms Replace Algorithms Find Iterators & Split Algorithms Exception Safety Concepts Definitions Finder Concept Formatter concept Reference Header <boost/algorithm/string/case_conv.hpp> Header <boost/algorithm/string/classification.hpp> Header <boost/algorithm/string/collection_traits.hpp> Header <boost/algorithm/string/compare.hpp> Header <boost/algorithm/string/concept.hpp> Header <boost/algorithm/string/constants.hpp> Header <boost/algorithm/string/erase.hpp> Header <boost/algorithm/string/find.hpp> Header <boost/algorithm/string/find_format.hpp> Header <boost/algorithm/string/find_iterator.hpp> Header <boost/algorithm/string/finder.hpp> Header <boost/algorithm/string/formatter.hpp> Header <boost/algorithm/string/iterator_range.hpp> Header <boost/algorithm/string/predicate.hpp> Header <boost/algorithm/string/regex.hpp> Header <boost/algorithm/string/regex_find_format.hpp> Header <boost/algorithm/string/replace.hpp> Header <boost/algorithm/string/sequence_traits.hpp> Header <boost/algorithm/string/split.hpp> Header <boost/algorithm/string/std_containers_traits.hpp> Header <boost/algorithm/string.hpp> Header <boost/algorithm/string_regex.hpp> Header <boost/algorithm/string/trim.hpp> Rationale Locales Regular Expressions Environment Build Examples Tests Portability Credits Acknowledgments Boost.Threads Overview Introduction Dangers C++ Standard Library usage in multithreaded programs Common guarantees for all Boost.Threads components Design Goals Iterative Phases Phase 1, Synchronization Primitives Phase 2, Thread Management and Thread Specific Storage The Next Phase Concepts Mutexes Read/Write Mutexes Rationale Rationale for the Creation of Boost.Threads Rationale for the Low Level Primitives Supported in Boost.Threads Rationale for the Lock Design Rationale for NonCopyable Thread Type Rationale for not providing Event Variables Reference Header <boost/thread/barrier.hpp> Header <boost/thread/condition.hpp> Header <boost/thread/exceptions.hpp> Header <boost/thread/mutex.hpp> Header <boost/thread/once.hpp> Header <boost/thread/recursive_mutex.hpp> Header <boost/thread/read_write_mutex.hpp> Header <boost/thread/thread.hpp> Header <boost/thread/tss.hpp> Header <boost/thread/xtime.hpp> Frequently Asked Questions Configuration Library Defined Public Macros Library Defined Implementation Macros Build Building the Boost.Threads Libraries Testing the Boost.Threads Libraries Implementation Notes Win32 Release Notes Boost 1.32.0 Acknowledgements Boost.Tribool Introduction Tutorial Basic usage Renaming the indeterminate state tribool input/output Reference Header <boost/logic/tribool.hpp> Header <boost/logic/tribool_fwd.hpp> Header <boost/logic/tribool_io.hpp> Testsuite Acceptance tests Boost.Variant Introduction Abstract Motivation Tutorial Basic Usage Advanced Topics Reference Concepts Header <boost/variant.hpp> Header <boost/variant/variant_fwd.hpp> Header <boost/variant/variant.hpp> Header <boost/variant/recursive_variant.hpp> Header <boost/variant/recursive_wrapper.hpp> Header <boost/variant/apply_visitor.hpp> Header <boost/variant/get.hpp> Header <boost/variant/bad_visit.hpp> Header <boost/variant/static_visitor.hpp> Header <boost/variant/visitor_ptr.hpp> Design Overview "Never-Empty" Guarantee Miscellaneous Notes Boost.Variant vs. Boost.Any Portability Troubleshooting Acknowledgments References
Documentation for some libraries is available in alternative formats:
•HTML (tarred, gzipped)•PDF•Unix man pages•DocBook•XSL Formatting ObjectsLibraries Listed AlphabeticallyLibraries Listed Alphabetically•Any -
Safe, generic container for single values of different value types
, from Kevlin Henney.•Array - STL compliant container wrapper for arrays of constant size, from Nicolai Josuttis.•Bind - Generalized binders for function/object/pointers and member functions, from Peter Dimov.•CRC - Cyclic Redundancy Code, from Daryle Walker.•Call Traits - Defines types for passing parameters, from John Maddock and Howard Hinnant.•Compatibility - Help for non-conforming standard libraries, from Ralf Grosse-Kunstleve and Jens Maurer.•Compose - Functional composition adapters for the STL, from Nicolai Josuttis.•Compressed Pair - Empty member optimization, from John Maddock and Howard Hinnant.•Concept Check - Tools for generic programming, from Jeremy Siek.•Config - Helps boost library developers adapt to compiler idiosyncrasies; not intended for library users, from John Maddock, Beman Dawes, and Vesa Karvonen.•Conversion - Numeric, polymorphic, and lexical casts, from Dave Abrahams and Kevlin Henney.•Date Time - A set of facilities to ease programming with dates and times.
, from Jeff Garland.•Dynamic Bitset - A runtime sized version of std::bitset, from Jeremy Siek and Chuck Allison.•Filesystem - Portable paths, iteration over directories, and other useful filesystem operations, from Beman Dawes.•Format - Type-safe 'printf-like' format operations, from Samuel Krempp.•Function - Function object wrappers for deferred calls or callbacks, from Douglas Gregor.•Functional - Enhanced function object adaptors, from Mark Rodgers.•Graph - Generic graph components and algorithms, from Jeremy Siek and University of Notre Dame Team.•I/O State Savers - Save I/O state to prevent jumbled data, from Daryle Walker.•Integer - Headers to ease dealing with integral types, from various authors.•Interval - Extends the usual arithmetic functions to mathematical intervals, from Guillaume Melquiond, Hervé Brönnimann, and Sylvain Pion.•Iterator Adaptors - Adapt a base type into a standard conforming iterator, from Dave Abrahams, Jeremy Siek, and John Potter.•Lambda - Define small unnamed function objects at the actual call site, and more, from Jaakko Järvi.•MPL - Template metaprogramming framework of compile-time algorithms, sequences and metafunction classes, from Aleksey Gurtovoy.•Math - Several contributions in the domain of mathematics, from various authors.•Math/Common Factor - Greatest common divisor and least common multiple, from Daryle Walker.•Math/Octonion - Octonions, from Hubert Holin.•Math/Quaternion - Quaternions, from Hubert Holin.•Math/Special Functions - Mathematical special functions such as atanh, sinc, and sinhc, from Hubert Holin.•Mem_fn - Generalized binders for member functions, from Peter Dimov.•Multi Array - Multidimensional containers and adaptors for arrays of contiguous data, from Ron Garcia.•Operators - Templates ease arithmetic classes and iterators, from Dave Abrahams and Jeremy Siek.•Optional - Discriminated-union wrapper for optional values, from Fernando Cacciola.•Pool - Memory pool management, from Steve Cleary.•Preprocessor - Preprocessor metaprogramming tools including repetition and recursion, from Vesa Karvonen and Paul Mensonides.•Program_options -
Facilities to obtain configuration data from command line, config files
and other sources, from Vladimir Prus.•Property Map - Concepts defining interfaces which map key objects to value objects, from Jeremy Siek.•Python - Reflects C++ classes and functions into Python, from Dave Abrahams.•Random - A complete system for random number generation, from Jens Maurer.•Rational - A rational number class, from Paul Moore.•Ref - A utility library for passing references to generic functions, from Jaakko Järvi, Peter Dimov, Douglas Gregor, and Dave Abrahams.•Regex - Regular expression library, from John Maddock.•Serialization - Serialization of C++ objects for persistence and marshalling, from Robert Ramey.•Signals - Managed signals & slots callback implementation, from Douglas Gregor.•Smart Pointer - Five smart pointer class templates, from Greg Colvin, Beman Dawes, Peter Dimov, and Darin Adler.•Spirit - LL parser framework represents parsers directly as EBNF grammars in inlined C++, from Joel de Guzman and team .•Static Assert - Static assertions (compile time assertions), from John Maddock.•String Algorithms -
A set of generic string-related algorithms and utilities
, from Pavol Droba.•Test - Support for simple program testing, full unit testing, and for program execution monitoring, from Gennadiy Rozental.•Threads - Portable C++ multi-threading, from William Kempf.•Timer - Event timer, progress timer, and progress display classes, from Beman Dawes.•Tokenizer - Break of a string or other character sequence into a series of tokens, from John Bandela.•Tribool - Three-state boolean type, from Douglas Gregor.•Tuple - Ease definition of functions returning multiple values, and more, from Jaakko Järvi.•Type Traits - Templates for fundamental properties of types, from John Maddock, Steve Cleary, and others .•Utility - Class noncopyable plus checked_delete, checked_array_delete, next, prior function templates, plus base-from-member idiom, from Dave Abrahams and others .•Variant - Safe, generic, stack-based discriminated union container, from Eric Friedman and Itay Maman.•uBLAS - Basic linear algebra for dense, packed and sparse matrices, from Joerg Walter and Mathias Koch.Libraries Listed by CategoryLibraries Listed by Category
String and text processing
String and text processing
•Format - Type-safe 'printf-like' format operations, from Samuel Krempp.•Regex - Regular expression library, from John Maddock.•String Algorithms -
A set of generic string-related algorithms and utilities
, from Pavol Droba.•Tokenizer - Break of a string or other character sequence into a series of tokens, from John Bandela.
Containers
Containers
•Array - STL compliant container wrapper for arrays of constant size, from Nicolai Josuttis.•Dynamic Bitset - A runtime sized version of std::bitset, from Jeremy Siek and Chuck Allison.•Graph - Generic graph components and algorithms, from Jeremy Siek and University of Notre Dame Team.•Multi Array - Multidimensional containers and adaptors for arrays of contiguous data, from Ron Garcia.•Property Map - Concepts defining interfaces which map key objects to value objects, from Jeremy Siek.•Variant - Safe, generic, stack-based discriminated union container, from Eric Friedman and Itay Maman.
Iterators
Iterators
•Graph - Generic graph components and algorithms, from Jeremy Siek and University of Notre Dame Team.•Iterator Adaptors - Adapt a base type into a standard conforming iterator, from Dave Abrahams, Jeremy Siek, and John Potter.•Operators - Templates ease arithmetic classes and iterators, from Dave Abrahams and Jeremy Siek.•Tokenizer - Break of a string or other character sequence into a series of tokens, from John Bandela.
Algorithms
Algorithms
•Graph - Generic graph components and algorithms, from Jeremy Siek and University of Notre Dame Team.•Utility - Class noncopyable plus checked_delete, checked_array_delete, next, prior function templates, plus base-from-member idiom, from Dave Abrahams and others .
Function objects and higher-order programming
Function objects and higher-order programming
•Bind - Generalized binders for function/object/pointers and member functions, from Peter Dimov.•Compose - Functional composition adapters for the STL, from Nicolai Josuttis.•Function - Function object wrappers for deferred calls or callbacks, from Douglas Gregor.•Functional - Enhanced function object adaptors, from Mark Rodgers.•Lambda - Define small unnamed function objects at the actual call site, and more, from Jaakko Järvi.•Mem_fn - Generalized binders for member functions, from Peter Dimov.•Ref - A utility library for passing references to generic functions, from Jaakko Järvi, Peter Dimov, Douglas Gregor, and Dave Abrahams.•Signals - Managed signals & slots callback implementation, from Douglas Gregor.
Generic programming
Generic programming
•Call Traits - Defines types for passing parameters, from John Maddock and Howard Hinnant.•Concept Check - Tools for generic programming, from Jeremy Siek.•Operators - Templates ease arithmetic classes and iterators, from Dave Abrahams and Jeremy Siek.•Property Map - Concepts defining interfaces which map key objects to value objects, from Jeremy Siek.•Static Assert - Static assertions (compile time assertions), from John Maddock.•Type Traits - Templates for fundamental properties of types, from John Maddock, Steve Cleary, and others .
Template metaprogramming
Template metaprogramming
•MPL - Template metaprogramming framework of compile-time algorithms, sequences and metafunction classes, from Aleksey Gurtovoy.•Static Assert - Static assertions (compile time assertions), from John Maddock.•Type Traits - Templates for fundamental properties of types, from John Maddock, Steve Cleary, and others .
Preprocessor metaprogramming
Preprocessor metaprogramming
•Preprocessor - Preprocessor metaprogramming tools including repetition and recursion, from Vesa Karvonen and Paul Mensonides.
Concurrent programming
Concurrent programming
•Threads - Portable C++ multi-threading, from William Kempf.
Math and numerics
Math and numerics
•Integer - Headers to ease dealing with integral types, from various authors.•Interval - Extends the usual arithmetic functions to mathematical intervals, from Guillaume Melquiond, Hervé Brönnimann, and Sylvain Pion.•Math - Several contributions in the domain of mathematics, from various authors.•Math/Common Factor - Greatest common divisor and least common multiple, from Daryle Walker.•Math/Octonion - Octonions, from Hubert Holin.•Math/Quaternion - Quaternions, from Hubert Holin.•Math/Special Functions - Mathematical special functions such as atanh, sinc, and sinhc, from Hubert Holin.•Multi Array - Multidimensional containers and adaptors for arrays of contiguous data, from Ron Garcia.•Operators - Templates ease arithmetic classes and iterators, from Dave Abrahams and Jeremy Siek.•Random - A complete system for random number generation, from Jens Maurer.•Rational - A rational number class, from Paul Moore.•uBLAS - Basic linear algebra for dense, packed and sparse matrices, from Joerg Walter and Mathias Koch.
Correctness and testing
Correctness and testing
•Concept Check - Tools for generic programming, from Jeremy Siek.•Static Assert - Static assertions (compile time assertions), from John Maddock.•Test - Support for simple program testing, full unit testing, and for program execution monitoring, from Gennadiy Rozental.
Data structures
Data structures
•Any -
Safe, generic container for single values of different value types
, from Kevlin Henney.•Compressed Pair - Empty member optimization, from John Maddock and Howard Hinnant.•Optional - Discriminated-union wrapper for optional values, from Fernando Cacciola.•Program_options -
Facilities to obtain configuration data from command line, config files
and other sources, from Vladimir Prus.•Tuple - Ease definition of functions returning multiple values, and more, from Jaakko Järvi.•Variant - Safe, generic, stack-based discriminated union container, from Eric Friedman and Itay Maman.
Input/Output
Input/Output
•Format - Type-safe 'printf-like' format operations, from Samuel Krempp.•I/O State Savers - Save I/O state to prevent jumbled data, from Daryle Walker.•Serialization - Serialization of C++ objects for persistence and marshalling, from Robert Ramey.
Inter-language support
Inter-language support
•Python - Reflects C++ classes and functions into Python, from Dave Abrahams.
Memory
Memory
•Pool - Memory pool management, from Steve Cleary.•Smart Pointer - Five smart pointer class templates, from Greg Colvin, Beman Dawes, Peter Dimov, and Darin Adler.•Utility - Class noncopyable plus checked_delete, checked_array_delete, next, prior function templates, plus base-from-member idiom, from Dave Abrahams and others .
Parsing
Parsing
•Spirit - LL parser framework represents parsers directly as EBNF grammars in inlined C++, from Joel de Guzman and team .
Miscellaneous
Miscellaneous
•CRC - Cyclic Redundancy Code, from Daryle Walker.•Compressed Pair - Empty member optimization, from John Maddock and Howard Hinnant.•Conversion - Numeric, polymorphic, and lexical casts, from Dave Abrahams and Kevlin Henney.•Date Time - A set of facilities to ease programming with dates and times.
, from Jeff Garland.•Filesystem - Portable paths, iteration over directories, and other useful filesystem operations, from Beman Dawes.•Optional - Discriminated-union wrapper for optional values, from Fernando Cacciola.•Timer - Event timer, progress timer, and progress display classes, from Beman Dawes.•Tribool - Three-state boolean type, from Douglas Gregor.•Utility - Class noncopyable plus checked_delete, checked_array_delete, next, prior function templates, plus base-from-member idiom, from Dave Abrahams and others .
Broken compiler workarounds
Broken compiler workarounds
•Compatibility - Help for non-conforming standard libraries, from Ralf Grosse-Kunstleve and Jens Maurer.•Config - Helps boost library developers adapt to compiler idiosyncrasies; not intended for library users, from John Maddock, Beman Dawes, and Vesa Karvonen.Boost.AnyBoost.AnyBoost.AnyKevlin HenneyCopyright © 2001 Kevlin HenneyIntroductionIntroductionThere are times when a generic (in the sense of
general as opposed to
template-based programming) type is needed:
variables that are truly variable, accommodating values of many
other more specific types rather than C++'s normal strict and
static types. We can distinguish three basic kinds of generic
type:•Converting types that can hold one of a number of
possible value types, e.g. int and
string, and freely convert between them, for
instance interpreting 5 as "5" or
vice-versa. Such types are common in scripting and other
interpreted
languages.
boost::lexical_cast
supports such conversion functionality.•
Discriminated types that contain values of different types but
do not attempt conversion between them, i.e. 5 is
held strictly as an int and is not implicitly
convertible either to "5" or to
5.0. Their indifference to interpretation but
awareness of type effectively makes them safe, generic
containers of single values, with no scope for surprises from
ambiguous conversions.•
Indiscriminate types that can refer to anything but are
oblivious to the actual underlying type, entrusting all forms
of access and interpretation to the programmer. This niche is
dominated by void *, which offers plenty of scope
for surprising, undefined behavior.The boost::any class
(based on the class of the same name described in "Valued
Conversions" by Kevlin Henney, C++
Report 12(7), July/August 2000) is a variant value type
based on the second category. It supports copying of any value
type and safe checked extraction of that value strictly against
its type. A similar design, offering more appropriate operators,
can be used for a generalized function adaptor,
any_function, a generalized iterator adaptor,
any_iterator, and other object types that need
uniform runtime treatment but support only compile-time template
parameter conformance.ExamplesExamplesThe following code demonstrates the syntax for using
implicit conversions to and copying of any objects:
#include <list>
#include <boost/any.hpp>
using boost::any_cast;
typedef std::list<boost::any> many;
void append_int(many & values, int value)
{
boost::any to_append = value;
values.push_back(to_append);
}
void append_string(many & values, const std::string & value)
{
values.push_back(value);
}
void append_char_ptr(many & values, const char * value)
{
values.push_back(value);
}
void append_any(many & values, const boost::any & value)
{
values.push_back(value);
}
void append_nothing(many & values)
{
values.push_back(boost::any());
}
The following predicates follow on from the previous
definitions and demonstrate the use of queries on any
objects:
bool is_empty(const boost::any & operand)
{
return operand.empty();
}
bool is_int(const boost::any & operand)
{
return operand.type() == typeid(int);
}
bool is_char_ptr(const boost::any & operand)
{
try
{
any_cast<const char *>(operand);
return true;
}
catch(const boost::bad_any_cast &)
{
return false;
}
}
bool is_string(const boost::any & operand)
{
return any_cast<std::string>(&operand);
}
void count_all(many & values, std::ostream & out)
{
out << "#empty == "
<< std::count_if(values.begin(), values.end(), is_empty) << std::endl;
out << "#int == "
<< std::count_if(values.begin(), values.end(), is_int) << std::endl;
out << "#const char * == "
<< std::count_if(values.begin(), values.end(), is_char_ptr) << std::endl;
out << "#string == "
<< std::count_if(values.begin(), values.end(), is_string) << std::endl;
}
The following type, patterned after the OMG's Property Service, defines name-value pairs for arbitrary value types:
struct property
{
property();
property(const std::string &, const boost::any &);
std::string name;
boost::any value;
};
typedef std::list<property> properties;
The following base class demonstrates one approach to
runtime polymorphism based callbacks that also require arbitrary
argument types. The absence of virtual member templates requires
that different solutions have different trade-offs in terms of
efficiency, safety, and generality. Using a checked variant type
offers one approach:
class consumer
{
public:
virtual void notify(const any &) = 0;
...
};
ReferenceReferenceValueType requirementsValues are strongly informational objects for which
identity is not significant, i.e. the focus is principally on
their state content and any behavior organized around
that. Another distinguishing feature of values is their
granularity: normally fine-grained objects representing simple
concepts in the system such as quantities.As the emphasis of a value lies in its state not its
identity, values can be copied and typically assigned one to
another, requiring the explicit or implicit definition of a
public copy constructor and public assignment operator. Values
typically live within other scopes, i.e. within objects or
blocks, rather than on the heap. Values are therefore normally
passed around and manipulated directly as variables or through
references, but not as pointers that emphasize identity and
indirection.The specific requirements on value types to be used in an
any
are:•A ValueType is
CopyConstructible [20.1.3].•A ValueType is
optionally Assignable [23.1]. The strong
exception-safety guarantee is required for all forms of
assignment.•The destructor for a
ValueType upholds the no-throw
exception-safety guarantee.AcknowledgementsAcknowledgementsDoug Gregor ported the documentation to the BoostBook format.Boost.ArrayBoost.ArrayBoost.ArrayNicolai JosuttisCopyright © 2001-2004 Nicolai M. JosuttisPermission to copy, use, modify, sell and distribute this
software is granted provided this copyright notice appears in
all copies. This software is provided "as is" without express or
implied warranty, and with no claim as to its suitability for
any purpose.IntroductionIntroductionThe C++ Standard Template Library STL as part of the C++
Standard Library provides a framework for processing algorithms on
different kind of containers. However, ordinary arrays don't
provide the interface of STL containers (although, they provide
the iterator interface of STL containers).As replacement for ordinary arrays, the STL provides class
std::vector. However,
std::vector<> provides
the semantics of dynamic arrays. Thus, it manages data to be able
to change the number of elements. This results in some overhead in
case only arrays with static size are needed.In his book, Generic Programming and the
STL, Matthew H. Austern introduces a useful wrapper
class for ordinary arrays with static size, called
block. It is safer and has no worse performance than
ordinary arrays. In The C++ Programming
Language, 3rd edition, Bjarne Stroustrup introduces a
similar class, called c_array, which I (Nicolai Josuttis) present
slightly modified in my book The C++ Standard Library -
A Tutorial and Reference, called
carray. This is the essence of these approaches
spiced with many feedback from boost.After considering different names, we decided to name this
class simply array.Note that this class is suggested to be part of the next
Technical Report, which will extend the C++ Standard (see
http://std.dkuug.dk/jtc1/sc22/wg21/docs/papers/2003/n1548.htm).Class array fulfills most
but not all of the requirements of "reversible containers" (see
Section 23.1, [lib.container.requirements] of the C++
Standard). The reasons array is not an reversible STL container is
because:
•No constructors are provided.•Elements may have an undetermined initial value (see the section called “Design Rationale”).•swap() has no constant complexity.•size() is always constant, based on the second template argument of the type.•The container provides no allocator support.It doesn't fulfill the requirements of a "sequence" (see Section 23.1.1, [lib.sequence.reqmts] of the C++ Standard), except that:
•front() and back() are provided.•operator[] and at() are provided.ReferenceReferenceDesign RationaleDesign RationaleThere was an important design tradeoff regarding the
constructors: We could implement array as an "aggregate" (see
Section 8.5.1, [dcl.init.aggr], of the C++ Standard). This would
mean:
•An array can be initialized with a
brace-enclosing, comma-separated list of initializers for the
elements of the container, written in increasing subscript
order:boost::array<int,4> a = { { 1, 2, 3 } };Note that if there are fewer elements in the
initializer list, then each remaining element gets
default-initialized (thus, it has a defined value).However, this approach has its drawbacks: passing no initializer list means that the elements
have an indetermined initial value, because the rule says
that aggregates may have:
•No user-declared constructors.•No private or protected non-static data members.•No base classes.•No virtual functions.Nevertheless, The current implementation uses this approach.Note that for standard conforming compilers it is possible to
use fewer braces (according to 8.5.1 (11) of the Standard). That is,
you can initialize an array as follows:boost::array<int,4> a = { 1, 2, 3 };
I'd appreciate any constructive feedback. Please note: I don't have time to read all boost
mails. Thus, to make sure that feedback arrives to me, please send
me a copy of each mail regarding this class.The code is provided "as is" without expressed or implied
warranty.For more information...For more information...To find more details about using ordinary arrays in C++ and
the framework of the STL, see e.g.
The C++ Standard Library - A Tutorial and Reference
by Nicolai M. Josuttis
Addison Wesley Longman, 1999
ISBN 0-201-37926-0Home Page of Nicolai
JosuttisAcknowledgementsAcknowledgementsDoug Gregor ported the documentation to the BoostBook format.Concept referenceConcept referenceCopyright © 2001, 2002 Indiana UniversityCopyright © 2000, 2001 University of Notre Dame du LacCopyright © 2000 Jeremy SiekLie-Quan LeeAndrew LumsdaineCopyright © 1996-1999 Silicon Graphics Computer Systems, Inc.Copyright © 1994 Hewlett-Packard CompanyThis product includes software developed at the University
of Notre Dame and the Pervasive Technology Labs at Indiana
University. For technical information contact Andrew Lumsdaine
at the Pervasive Technology Labs at Indiana University. For
administrative and license questions contact the Advanced
Research and Technology Institute at 351 West 10th Street.
Indianapolis, Indiana 46202, phone 317-278-4100, fax
317-274-5902.Some concepts based on versions from the MTL draft manual
and Boost Graph and Property Map documentation, the SGI Standard
Template Library documentation and the Hewlett-Packard STL,
under the following license:
ConceptsConcepts•Assignable•InputIterator•OutputIterator•ForwardIterator•BidirectionalIterator•RandomAccessIterator•DefaultConstructible•CopyConstructible•EqualityComparable•LessThanComparable•SignedIntegerConcept AssignableConcept AssignableAssignableDescriptionDescriptionAssignable types must have copy constructors,
operator= for assignment, and the swap()
function defined.Refinement ofRefinement of•CopyConstructibleNotationNotationXA type playing the role of assignable-type in the Assignable concept.x, y, Objects of type XValid expressionsValid expressionsNameExpressionTypeSemanticsAssignmentx = yX &Require operator=Swapswap(x, y)voidRequire swap() functionModelsModels•intSee alsoSee also•CopyConstructibleConcept InputIteratorConcept InputIteratorInputIteratorDescriptionDescriptionAn input iterator is an iterator that can read through a sequence of
values. It is single-pass (old values of the iterator cannot be
re-used), and read-only.An input iterator represents a position in a sequence. Therefore, the
iterator can point into the sequence (returning a value when dereferenced
and being incrementable), or be off-the-end (and not dereferenceable or
incrementable).Refinement ofRefinement of•Assignable•DefaultConstructible•EqualityComparableAssociated typesAssociated types•value_typestd::iterator_traits<Iter>::value_typeThe value type of the iterator (not necessarily what
*i returns)•difference_typestd::iterator_traits<Iter>::difference_typeThe difference type of the iterator•categorystd::iterator_traits<Iter>::iterator_categoryThe category of the iteratorNotationNotationIterA type playing the role of iterator-type in the InputIterator concept.i, j, Objects of type IterxObject of type value_typeType expressionsType expressionsCategory tagcategory must be
derived from std::input_iterator_tag, a model of DefaultConstructible, and a model of CopyConstructible.
Value type copy constructibilityvalue_type must be
a model of CopyConstructible.
Difference type propertiesdifference_type must be
a model of SignedInteger.
Valid expressionsValid expressionsNameExpressionTypePreconditionSemanticsPostconditionDereference*iConvertible to value_typei is incrementable (not
off-the-end) Preincrement++iIter &i is incrementable (not
off-the-end) Postincrementi++i is incrementable (not
off-the-end)Equivalent to (void)(++i)i is dereferenceable or
off-the-endPostincrement and dereference*i++Convertible to value_typei is incrementable (not
off-the-end)Equivalent to {value_type t = *i; ++i; return t;}i is dereferenceable or
off-the-endComplexityComplexity
All iterator operations must take amortized constant time.
ModelsModels•std::istream_iteratorSee alsoSee also•DefaultConstructible•EqualityComparable•ForwardIterator•OutputIteratorConcept OutputIteratorConcept OutputIteratorOutputIteratorDescriptionDescriptionAn output iterator is an iterator that can write a sequence of
values. It is single-pass (old values of the iterator cannot be
re-used), and write-only.An output iterator represents a position in a (possibly infinite)
sequence. Therefore, the iterator can point into the sequence (returning
a value when dereferenced and being incrementable), or be off-the-end
(and not dereferenceable or incrementable).Associated typesAssociated types•value_typestd::iterator_traits<Iter>::value_typeThe stated value type of the iterator (should be
void for an output iterator that does not model some other
iterator concept).•difference_typestd::iterator_traits<Iter>::difference_typeThe difference type of the iterator•categorystd::iterator_traits<Iter>::iterator_categoryThe category of the iteratorNotationNotationIterA type playing the role of iterator-type in the OutputIterator concept.ValueTypeA type playing the role of value-type in the OutputIterator concept.i, j, Objects of type IterxObject of type ValueTypeType expressionsType expressionsThe type Iter must be a model of Assignable.The type ValueType must be a model of Assignable.The type Iter must be a model of DefaultConstructible.The type Iter must be a model of
EqualityComparable.Category tagcategory must be
derived from std::output_iterator_tag, a model of DefaultConstructible, and a model of CopyConstructible.
Difference type propertiesdifference_type must be
a model of SignedInteger.
Valid expressionsValid expressionsNameExpressionTypePreconditionSemanticsPostconditionDereference*ii is incrementable (not
off-the-end) Dereference and assign*i = xi is incrementable (not
off-the-end) *i may not be written to again until it has
been incremented.Preincrement++iIter &i is incrementable (not
off-the-end) Postincrementi++i is incrementable (not
off-the-end)Equivalent to (void)(++i)i is dereferenceable or
off-the-endPostincrement, dereference, and assign*i++ = xi is incrementable (not
off-the-end)Equivalent to {*i = t; ++i;}i is dereferenceable or
off-the-endComplexityComplexity
All iterator operations must take amortized constant time.
ModelsModels•std::ostream_iterator, ..., •std::insert_iterator, ..., •std::front_insert_iterator, ..., •std::back_insert_iterator, ..., See alsoSee alsoConcept ForwardIteratorConcept ForwardIteratorForwardIteratorDescriptionDescriptionA forward iterator is an iterator that can read through a sequence of
values. It is multi-pass (old values of the iterator can be
re-used), and can be either mutable (data pointed to by it can be
changed) or not mutable.An iterator represents a position in a sequence. Therefore, the
iterator can point into the sequence (returning a value when dereferenced
and being incrementable), or be off-the-end (and not dereferenceable or
incrementable).Refinement ofRefinement of•InputIterator•OutputIteratorAssociated typesAssociated types•value_typestd::iterator_traits<Iter>::value_typeThe value type of the iterator•categorystd::iterator_traits<Iter>::iterator_categoryThe category of the iteratorNotationNotationIterA type playing the role of iterator-type in the ForwardIterator concept.i, j, Objects of type IterxObject of type value_typeType expressionsType expressionsCategory tagcategory must be
derived from std::forward_iterator_tag.
Valid expressionsValid expressionsNameExpressionTypePreconditionSemanticsPostconditionDereference*iconst-if-not-mutable value_type &i is incrementable (not
off-the-end) Member accessi->{member-name} (return type is pointer-to-object type)const-if-not-mutable value_type *i is incrementable (not
off-the-end) Preincrement++iIter &i is incrementable (not
off-the-end) Postincrementi++Iteri is incrementable (not
off-the-end)Equivalent to {Iter j = i; ++i; return j;}i is dereferenceable or
off-the-endComplexityComplexity
All iterator operations must take amortized constant time.
InvariantsInvariantsPredecrement must return object&i = &(++i)Unique path through sequencei == j implies ++i == ++jModelsModels•T *•std::hash_set<T>::iteratorSee alsoSee also•BidirectionalIteratorConcept BidirectionalIteratorConcept BidirectionalIteratorBidirectionalIteratorDescriptionDescriptionA bidirectional iterator is an iterator that can read through a sequence
of values. It can move in either direction through the sequence, and can
be either mutable (data pointed to by it can be changed) or not mutable.An iterator represents a position in a sequence. Therefore, the
iterator can point into the sequence (returning a value when dereferenced
and being incrementable), or be off-the-end (and not dereferenceable or
incrementable).Refinement ofRefinement of•ForwardIteratorAssociated typesAssociated types•value_typestd::iterator_traits<Iter>::value_typeThe value type of the iterator•categorystd::iterator_traits<Iter>::iterator_categoryThe category of the iteratorNotationNotationIterA type playing the role of iterator-type in the BidirectionalIterator concept.i, j, Objects of type IterxObject of type value_typeType expressionsType expressionsCategory tagcategory must be
derived from std::bidirectional_iterator_tag.
Valid expressionsValid expressionsNameExpressionTypePreconditionSemanticsPostconditionPredecrement--iIter &i is incrementable (not
off-the-end) and some dereferenceable iterator j exists
such that i == ++j Postdecrementi--IterSame as for predecrementEquivalent to {Iter j = i; --i; return j;}i is dereferenceable or
off-the-endComplexityComplexity
All iterator operations must take amortized constant time.
InvariantsInvariantsPredecrement must return object&i = &(--i)Unique path through sequencei == j implies --i == --jIncrement and decrement are inverses++i; --i; and --i; ++i; must end up with the
value of i unmodified, if i both of the
operations in the pair are valid.
ModelsModels•T *•std::list<T>::iteratorSee alsoSee also•RandomAccessIteratorConcept RandomAccessIteratorConcept RandomAccessIteratorRandomAccessIteratorDescriptionDescriptionA random access iterator is an iterator that can read through
a sequence of values. It can move in either direction through the
sequence (by any amount in constant time), and can be either mutable
(data pointed to by it can be changed) or not mutable.An iterator represents a position in a sequence. Therefore,
the iterator can point into the sequence (returning a value when
dereferenced and being incrementable), or be off-the-end (and not
dereferenceable or incrementable).Refinement ofRefinement of•BidirectionalIterator•LessThanComparableAssociated typesAssociated types•value_typestd::iterator_traits<Iter>::value_typeThe value type of the iterator•categorystd::iterator_traits<Iter>::iterator_categoryThe category of the iterator•difference_typestd::iterator_traits<Iter>::difference_typeThe difference type of the iterator (measure of the number
of steps between two iterators)NotationNotationIterA type playing the role of iterator-type in the RandomAccessIterator concept.i, j, Objects of type IterxObject of type value_typenObject of type difference_typeint_offObject of type intType expressionsType expressionsCategory tagcategory must be
derived from std::random_access_iterator_tag.
Valid expressionsValid expressionsNameExpressionTypeSemanticsMotioni += nIter &Equivalent to applying i++n times
if n is positive, applying i---n times if n is negative, and to a null
operation if n is zero.Motion (with integer offset)i += int_offIter &Equivalent to applying i++n times
if n is positive, applying i---n times if n is negative, and to a null
operation if n is zero.Subtractive motioni -= nIter &Equivalent to i+=(-n)Subtractive motion (with integer offset)i -= int_offIter &Equivalent to i+=(-n)Additioni + nIterEquivalent to {Iter j = i; j += n; return j;}Addition with integeri + int_offIterEquivalent to {Iter j = i; j += n; return j;}Addition (count first)n + iIterEquivalent to i + nAddition with integer (count first)int_off + iIterEquivalent to i + nSubtractioni - nIterEquivalent to i + (-n)Subtraction with integeri - int_offIterEquivalent to i + (-n)Distancei - jdifference_typeThe number of times i must be incremented (or
decremented if the result is negative) to reach j. Not
defined if j is not reachable from
i.Element accessi[n]const-if-not-mutable value_type &Equivalent to *(i + n)Element access with integer indexi[int_off]const-if-not-mutable value_type &Equivalent to *(i + n)ComplexityComplexity
All iterator operations must take amortized constant time.
ModelsModels•T *•std::vector<T>::iterator•std::vector<T>::const_iterator•std::deque<T>::iterator•std::deque<T>::const_iteratorSee alsoSee also•LessThanComparableConcept DefaultConstructibleConcept DefaultConstructibleDefaultConstructibleDescriptionDescriptionDefaultConstructible objects only need to have a default
constructor.NotationNotationXA type playing the role of default-constructible-type in the DefaultConstructible concept.Valid expressionsValid expressionsNameExpressionTypeSemanticsConstructionX()XConstruct an instance of the type with default parameters.ModelsModels•int•std::vector<double>Concept CopyConstructibleConcept CopyConstructibleCopyConstructibleDescriptionDescriptionCopy constructible types must be able to be constructed from another
member of the type.NotationNotationXA type playing the role of copy-constructible-type in the CopyConstructible concept.x, y, Objects of type XValid expressionsValid expressionsNameExpressionTypeSemanticsCopy constructionX(x)XRequire copy constructor.ModelsModels•intConcept EqualityComparableConcept EqualityComparableEqualityComparableDescriptionDescriptionEquality Comparable types must have == and
!= operators.NotationNotationXA type playing the role of comparable-type in the EqualityComparable concept.x, y, Objects of type XValid expressionsValid expressionsNameExpressionTypeEquality testx == yConvertible to boolInequality testx != yConvertible to boolModelsModels•int•std::vector<int>Concept LessThanComparableConcept LessThanComparableLessThanComparableDescriptionDescriptionLessThanComparable types must have <,
>, <=, and >=
operators.NotationNotationXA type playing the role of comparable-type in the LessThanComparable concept.x, y, Objects of type XValid expressionsValid expressionsNameExpressionTypeSemanticsLess thanx < yConvertible to boolDetermine if one value is less than another.Less than or equalx <= yConvertible to boolDetermine if one value is less than or equal to another.Greater thanx > yConvertible to boolDetermine if one value is greater than another.Greater than or equal tox >= yConvertible to boolDetermine if one value is greater than or equal to another.ModelsModels•intConcept SignedIntegerConcept SignedIntegerSignedIntegerRefinement ofRefinement of•CopyConstructible•Assignable•DefaultConstructible•EqualityComparable•LessThanComparableNotationNotationTA type playing the role of integral-type in the SignedInteger concept.x, y, z, Objects of type Ta, b, Objects of type intType expressionsType expressionsConversion to intT must be
convertible to int.
Valid expressionsValid expressionsNameExpressionTypeConversion from intT(a)TPreincrement++xT &Predecrement--xT &Postincrementx++TPostdecrementx--TSumx + yTSum with intx + aTSum-assignmentx += yT &Sum-assignment with intx += aT &Differencex - yTDifference with intx - aTProductx * yTProduct with intx * aTProduct-assignment with intx *= aT &Product with int on lefta * xTQuotientx / yTQuotient with intx / aTRight-shiftx >> yTRight-shift with intx >> aTRight-shift-assignment with intx >>= aT &Less-than comparisonx < yConvertible to boolLess-than comparison with intx < aConvertible to boolLess-than comparison with size_tx < boost::sample_value < std::size_t >()Convertible to boolGreater-than comparisonx > yConvertible to boolGreater-than comparison with intx > aConvertible to boolLess-than-or-equal comparisonx <= yConvertible to boolLess-than-or-equal comparison with intx <= aConvertible to boolGreater-than-or-equal comparisonx >= yConvertible to boolGreater-than-or-equal comparison with intx >= aConvertible to boolGreater-than-or-equal comparison with int on lefta >= xConvertible to boolEquality comparisonx == yConvertible to boolEquality comparison with intx == aConvertible to boolSee alsoSee alsoBoost.Date_TimeBoost.Date_TimeBoost.Date_TimeJeff GarlandCopyright © 2001-2004 CrystalClear Software, IncSubject to the Boost Software License, Version 1.0. (See accompanying file
LICENSE_1_0.txt or copy at http://www.boost.org/LICENSE_1_0.txt)IntroductionIntroduction
A set of date-time libraries based on generic programming concepts.
ConceptualConceptualMotivation
The motivation for this library comes from working with and helping build several date-time libraries on several projects. Date-time libraries provide fundamental infrastructure for most development projects. However, most of them have limitations in their ability to calculate, format, convert, or perform some other functionality. For example, most libraries do not correctly handle leap seconds, provide concepts such as infinity, or provide the ability to use high resolution or network time sources. These libraries also tend to be rigid in their representation of dates and times. Thus customized policies for a project or subproject are not possible.
Programming with dates and times should be almost as simple and natural as programming with strings and integers. Applications with lots of temporal logic can be radically simplified by having a robust set of operators and calculation capabilities. Classes should provide the ability to compare dates and times, add lengths or time durations, retrieve dates and times from clocks, and work naturally with date and time intervals.
Another motivation for development of the library was to apply modern C++ library design techniques to the date-time domain. Really to build a framework for the construction of building temporal types. For example, by providing iterators and traits classes to control fundamental properties of the library. To the authors knowledge this library is the only substantial attempt to apply modern C++ to a date-time library.
Domain Concepts
The date time domain is rich in terminology and problems.
The following is a brief introduction to the concepts you
will find reflected in the library.
The library supports 3 basic temporal types:
•Time Point -- Specifier
for a location in the time continuum.
•Time Duration -- A
length of time unattached to any point on the time continuum.
•Time Interval -- A duration
of time attached to a specific point in the time continuum.
Also known as a time period.
Each of these temporal types has a Resolution which is defined by the smallest representable duration. A Time system provides all these categories of temporal types as well as the rules for labeling and calculating with time points. Calendar Systems are simply time systems with a maximum resolution of one day. The Gregorian system is the most widely used calendar system today (the ISO system is basically a derivative of this). However, there are many other calendar systems as well. UTC (Coordinated Universal Time) is a widely used civil time system. UTC is adjusted for earth rotation at longitude 0 by the use of leap seconds (This is not predictable, only as necessary). Most local time systems are based on UTC but are also adjusted for earth rotation so that daylight hours are similar everywhere. In addition, some local times include daylight savings time (DST) adjustments to shift the daylight hours during the summer.
A Clock Device is software component (tied to some hardware) that provides the current date or time with respect to a time system. A clock can measure the current time to a known resolution which may be higher or lower than a particular time representation.
The library provides support for calculating with dates and times. However, time calculations are not quite the same as calculating with integers. If you are serious about the accuracy of your time calculations need to read about Stability, Predictability, and Approximations.
•Basic Terminology•Calculations•Stability, Predictability, and Approximations•ReferencesDesign Concepts
A large part of the genesis of this library has been the observation that few date-time libraries are built in a fashion that allows customization and extension. A typical example, the calendar logic is built directly into the date class. Or the clock retrieval functions are built directly into the time class. These design decisions usually make it impossible to extend or change the library behavior. At a more fundamental level, there are usually assumptions about the resolution of time representation or the gregorian calendar.
Often times, the result is that a project must settle for a less than complete library because of a requirement for high resolution time representation or other assumptions that do not match the implementation of the library. This is extremely unfortunate because development of a library of this sort is far from a trivial task.
While the design is far from perfect the current design is far more flexible than any date-time library the author is aware of. It is expected that the various aspects of extensibility will be better documented in future versions. Information about the design goals of the library is summarized here.
More Information
The design of the library is currently being evolved using
Wiki and email discussions. You can find more information at:
•Boost Wiki GDTL Start Page•Full Doxygen Reference ManualGregorianGregorianGregorian Date SystemGregorian Date SystemIntroduction --
Usage ExamplesIntroductionIntroductionThe gregorian date system provides a date programming system based the Gregorian Calendar. The first introduction of the Gregorian calendar was in 1582 to fix an error in the Julian Calendar. However, many local jurisdictions did not adopt this change until much later. Thus there is potential confusion with historical dates.
The implemented calendar is a "propleptic Gregorian calendar" which extends dates back prior to the Gregorian Calendar's first adoption in 1582. The current implementation supports dates in the range 1400-Jan-01 to 10000-Jan-01. Many references will represent dates prior to 1582 using the Julian Calendar, so caution is in order if accurate calculations are required on historic dates. See Calendrical Calculations by Reingold & Dershowitz for more details. Date information from Calendrical Calculations has been used to cross-test the correctness of the Gregorian calendar implementation.
All types for the gregorian system are found in namespace boost::gregorian. The library supports a convenience header boost/date_time/gregorian/gregorian_types.hpp that will include all the classes of the library with no input/output dependency. Another header boost/date_time/gregorian/gregorian.hpp will include the types and the input/output code.
The class boost::gregorian::date is the primary temporal type for users. If you are interested in learning about writing programs do specialized date calculations such as finding the "first sunday in april" see the date generators and algorithms page.
Usage ExamplesUsage ExamplesExampleDescriptionDays AliveDays Till New YearSimple date arithmetic. Retrieve current day from clock.Dates as stringsSimple parsing and formatting of dates from/to stringsDate Period CalculationsSee if a date is in a set of date periods (eg: is it a holiday/weekend)Print a monthSmall utility program which prints out all the days in a month from command line. Need to know if 1999-Jan-1 was a Friday or a Saturday? This program shows how to do it.Print HolidaysUses date generators to convert abstract specification into concrete set of dates.Date ClassIntroduction --
Header --
Construction --
Construct from String --
Construct from Clock --
Accessors --
Convert to String --
OperatorsIntroductionIntroduction
The class boost::gregorian::date is the primary interface for date programming. In general, the date class is immutable once constructed although it does allow assignment.
Other techniques for creating dates include date iterators and date algorithms or generators.
HeaderHeader
#include "boost/date_time/gregorian/gregorian.hpp" //include all types plus i/o
or
#include "boost/date_time/gregorian/gregorian_types.hpp" //no i/o just types
ConstructionConstructionSyntaxDescriptionExampledate(greg_year year, greg_month month, greg_day day)Construct from parts of date. Throws bad_year, bad_day_of_month, or bad_day_month (derivatives of std::out_of_range) if the year, month or day are out of range.date d(2002,Jan,10)date(date d)Copy constructordate d1(d)date(special_values sv)Constructor for infinities, not-a-date-time, max_date_time, and min_date_time
date d1(neg_infin);
date d2(pos_infin);
date d3(not_a_date_time);
date d4(max_date_time);
date d5(min_date_time);date;Default constructor. Creates a date object initialized to not_a_date_time. NOTE: this constructor can be disabled by defining DATE_TIME_NO_DEFAULT_CONSTRUCTOR (see compiler_config.hpp)date d; // d => not_a_date_timeConstruct from StringConstruct from StringSyntaxDescriptionExampledate from_string(const std::string&)From delimited date string where with order year-month-day eg: 2002-1-25
std::string ds("2002/1/25");
date d(from_string(ds))date from_undelimited_string(const std::string&)From iso type date string where with order year-month-day eg: 20020125
std::string ds("20020125");
date d(from_undelimited_string(ds))Construct from ClockConstruct from ClockSyntaxDescriptionExampleday_clock::local_day()Get the local day based on the time zone settings of the computer.date d(day_clock::local_day())day_clock::universal_day()Get the UTC day.date d(day_clock::universal_day())AccessorsAccessorsSyntaxDescriptionExamplegreg_year year() constGet the year part of the date.
date d(2002,Jan,10);
d.year() --> 2002;greg_month month() constGet the month part of the date.
date d(2002,Jan,10);
d.month() --> 1;greg_day day() const Get the day part of the date.
date d(2002,Jan,10);
d.day() --> 10;greg_ymd year_month_day() constReturn a year_month_day struct. More efficient when all 3 parts of the date are needed.
date d(2002,Jan,10);
date::ymd_type ymd = d.year_month_day();
ymd.year --> 2002, ymd.month --> 1, ymd.day --> 10greg_day_of_week day_of_week() constGet the day of the week (eg: Sunday, Monday, etc.
date d(2002,Jan,10);
d.day() --> Thursday;bool is_infinity() constReturns true if date is either positive or negative infinity
date d(pos_infin);
d.is_infinity() --> true;bool is_neg_infinity() constReturns true if date is negative infinity
date d(neg_infin);
d.is_neg_infinity() --> true;bool is_pos_infinity() constReturns true if date is positive infinity
date d(neg_infin);
d.is_pos_infinity() --> true;bool is_not_a_date() constReturns true if value is not a date
date d(not_a_date_time);
d.is_not_a_date() --> true;long modjulian_day() constReturns the modified julian day for the date. long julian_day() constReturns the julian day for the date. int week_number() constReturns the ISO 8601 week number for the date. Convert to StringConvert to StringSyntaxDescriptionExamplestd::string to_simple_string(date d)To YYYY-mmm-DD string where mmm 3 char month name.2002-Jan-01std::string to_iso_string(date d)To YYYYMMDD where all components are integers.20020131std::string to_iso_extended_string(date d) To YYYY-MM-DD where all components are integers.2002-01-31OperatorsOperatorsSyntaxDescriptionExampleoperator<<Stream output operator
date d(2002,Jan,1)
std::cout << d << std::endl;
operator==, operator!=,
operator>, operator<
operator>=, operator<=A full complement of comparison operatorsd1 == d2, etcdate operator+(date_duration) constReturn a date adding a day offset
date d(2002,Jan,1);
date_duration dd(1);
date d2 = d + dd;
date operator-(date_duration) constReturn a date by adding a day offset
date d(2002,Jan,1);
date_duration dd(1);
date d2 = d - dd;
date_duration operator-(date) constReturn a date duration by subtracting two dates
date d1(2002,Jan,1);
date d2(2002,Jan,2);
date_duration dd = d2-d1;
topDate Duration (aka Days)Introduction --
Header --
Construction --
OperatorsIntroductionIntroduction
As of version 1_32 the date_duration class has been typdefed as days in the boost::gregorian namespace. Throughout the examples you will find days used instead of date_duration.
The class boost::gregorian::date_duration is a simple day count used for arithmetic with gregorian::date. A duration can be either positive or negative.
HeaderHeader
#include "boost/date_time/gregorian/gregorian.hpp" //include all types plus i/o
or
#include "boost/date_time/gregorian/gregorian_types.hpp" //no i/o just types
ConstructionConstructionSyntaxDescriptionExampledate_duration(long)Create a duration count. date_duration dd(3); //3 daysAccessorsAccessorsSyntaxDescriptionExamplelong days() const Get the day count.date_duration dd(3); dd.days() --> 3bool is_negative() constTrue if number of days is less than zero.date_duration dd(-1); dd.is_negative() --> truestatic date_duration unit()Return smallest possible unit of duration type.date_duration::unit() --> date_duration(1)OperatorsOperatorsSyntaxDescriptionExample
operator==, operator!=,
operator>, operator<
operator>=, operator<=
A full complement of comparison operatorsdd1 == dd2, etcdate_duration operator+(date_duration) constAdd date durations.
date_duration dd1(3);
date_duration dd2(5);
date_duration dd3 = dd1 + dd2;
date_duration operator-(date_duration) constSubtract durations.
date_duration dd1(3);
date_duration dd2(5);
date_duration dd3 = dd1 - dd2;
topDate PeriodIntroduction --
Header --
Construction --
Accessors --
Convert to String --
OperatorsIntroductionIntroduction
The class boost::gregorian::date_period provides direct representation for ranges between two dates. Periods provide the ability to simplify some types of calculations by simplifying the conditional logic of the program. For example, testing if a date is within an irregular schedule such as a weekend or holiday can be accomplished using collections of date periods. This is facilitated by several methods that allow evaluation if a date_period intersects with another date period, and to generate the period resulting from the intersection. The period calculation example provides an example of this.
Date periods used in combination with infinity values have the ability to represent complex concepts such as 'until further notice'.
HeaderHeader
#include "boost/date_time/gregorian/gregorian.hpp" //include all types plus i/o
or
#include "boost/date_time/gregorian/gregorian_types.hpp" //no i/o just types
ConstructionConstructionSyntaxDescriptionExampledate_period(date begin, date end) Create a period as [begin, end). If last is <= begin then the period will be defined as null.date_period dp(date(2002,Jan,10), date(2002,Jan,12));date_period(date start, date_duration len) Create a period as [begin, begin+len). If len is <= zero then the period will be defined as null.date_period dp(date(2002,Jan,10), date_duration(2));date_period(date_period rhs) Copy constructor date_period dp1(dp)AccessorsAccessorsSyntaxDescriptionExampledate begin() const Return first day of period.
date_period dp(date(2002,Jan,1), date(2002,Jan,10));
dp.begin() --> 2002-Jan-01
date last() constReturn last date in the period
date_period dp(date(2002,Jan,1), date(2002,Jan,10));
dp.last() --> 2002-Jan-09
date end() constReturn one past the last in period
date_period dp(date(2002,Jan,1), date(2002,Jan,10));
dp.end() --> 2002-Jan-10
date_duration length() constReturn the length of the date_period
date_period dp(date(2002,Jan,1), date_duration(2));
dp.length() --> 2
bool is_null() constTrue if period is not well formed. eg: start less than end
date_period dp(date(2002,Jan,10), date(2002,Jan,1));
dp.begin() --> true
bool contains(date) constTrue if date is within the period
date_period dp(date(2002,Jan,1), date(2002,Jan,10));
dp.contains(date(2002,Jan,2)) --> true
bool contains(date_period) constTrue if date period is within the period
date_period dp1(date(2002,Jan,1), date(2002,Jan,10));
date_period dp2(date(2002,Jan,2), date(2002,Jan,3));
dp1.contains(dp2) --> true
dp2.contains(dp1) --> false
bool intersects(date_period) constTrue if periods overlap
date_period dp1(date(2002,Jan,1), date(2002,Jan,10));
date_period dp2(date(2002,Jan,2), date(2002,Jan,3));
dp2.intersects(dp1) --> true
date_period intersection(date_period) constCalculate the intersection of 2 periods. Null if no intersection.
date_period dp1(date(2002,Jan,1), date(2002,Jan,10));
date_period dp2(date(2002,Jan,2), date(2002,Jan,3));
dp2.intersection(dp1) --> dp2
date_period is_adjacent(date_period) constCheck if two periods are adjacent, but not overlapping.
date_period dp1(date(2002,Jan,1), date(2002,Jan,3));
date_period dp2(date(2002,Jan,3), date(2002,Jan,10));
dp2.is_adjacent(dp1) --> true
date_period is_after(date) constDetermine the period is after a given date.
date_period dp1(date(2002,Jan,10), date(2002,Jan,30));
date d(2002,Jan,3);
dp1.is_after(d) --> true
date_period is_before(date) constDetermine the period is before a given date.
date_period dp1(date(2002,Jan,1), date(2002,Jan,3));
date d(2002,Jan,10);
dp1.is_before(d) --> true
date_period merge(date_period) constReturns union of two periods. Null if no intersection.
date_period dp1(date(2002,Jan,1), date(2002,Jan,10));
date_period dp2(date(2002,Jan,9), date(2002,Jan,31));
dp2.merge(dp1) --> 2002-Jan-01/2002-Jan-31
date_period span(date_period) constCombines two periods and any gap between them such that start = min(p1.start, p2.start) and end = max(p1.end , p2.end)
date_period dp1(date(2002,Jan,1), date(2002,Jan,5));
date_period dp2(date(2002,Jan,9), date(2002,Jan,31));
dp2.hull(dp1) --> 2002-Jan-01/2002-Jan-31
date_period shift(date_duration)Add duration to both start and end.
date_period dp1(date(2002,Jan,1), date(2002,Jan,10));
dp1.shift(date_duration(1)); --> 2002-Jan-02/2002-Jan-11
Convert to StringConvert to StringSyntaxDescriptionExamplestd::string to_simple_string(date_period dp)To [YYYY-mmm-DD/YYYY-mmm-DD] string where mmm is 3 char month name.[2002-Jan-01/2002-Jan-31]OperatorsOperatorsSyntaxDescriptionExampleoperator<<ostream operator for date_period. Uses facet to format time points. Typical output: [2002-Jan-01/2002-Jan-31].std::cout << dp << std::endl;
operator==, operator!=,
operator>, operator<
A full complement of comparison operators dp1 == dp2, etcoperator<True if dp1.end() less than dp2.begin() dp1 < dp2, etcoperator>True if dp1.begin() greater than dp2.end()dp1 > dp2, etctopDate IteratorsIntroduction --
Header --
OverviewIntroductionIntroduction
Date iterators provide a standard mechanism for iteration through dates. Date iterators are a model of Input Iterator and can be used to populate collections with dates and other date generation tasks. For example, the print month example iterates through all the days in a month and prints them.
All of the iterators here derive from boost::gregorian::date_iterator.
HeaderHeader
#include "boost/date_time/gregorian/gregorian.hpp" //include all types plus i/o
or
#include "boost/date_time/gregorian/gregorian_types.hpp" //no i/o just types
OverviewOverviewClassConstruction ParametersDescriptiondate_iterator Common base class for all day level iterators.day_iteratordate start_date, int day_count=1Iterate day_count days at a time.week_iterator date start_date, int week_offset=1Iterate week_offset weeks at a time.month_iteratordate start_date, int month_offset=1
Iterate month_offset months. There are special rules for handling the end of the month. These are: if start date is last day of the month, always adjust to last day of the month. If date is beyond the end of the month (eg: jan 31 + 1 month) adjust back to end of month.
year_iteratordate start_date, int year_offset=1Iterate year_offset years. The year_iterator will always land on the day of the date parameter except when date is Feb 28 in a non-leap year. In this case the iterator will return Feb 29 for leap years (eg: 2003-Feb-28, 2004-Feb-29, 2005-Feb-28).topDate Generators/AlgorithmsDate Generators/AlgorithmsDate Generators/AlgorithmsIntroduction --
Header --
Class Overview --
Function OverviewIntroductionIntroduction
Date algorithms or generators are tools for generating other dates or schedules of dates. A generator function starts with some part of a date such as a month and day and is supplied another part to then generate a concrete date. This allows the programmer to represent concepts such as "The first Sunday in February" and then create a concrete set of dates when provided with one or more years.
Note: As of boost version 1_31_0, date generator names have been changed. Old names are still available but are no longer documented and may someday be deprecated
Also provided are stand-alone functions for generating a date, or calculation a duration of days. These functions take a date object and a weekday object as parameters.
All date generator classes and functions are in the boost::gregorian namespace.
The print holidays example shows a detailed usage example.
HeaderHeader
#include "boost/date_time/date_generators.hpp"
OverviewOverviewClassConstruction Parametersget_date ParameterDescriptionExampleyear_based_generatorabstract base classgreg_year yearA unifying date_generator base type for: partial_date, nth_day_of_the_week_in_month, first_day_of_the_week_in_month, and last_day_of_the_week_in_month
The print holidays example shows a detailed usage example.
last_day_of_the_week_in_monthgreg_weekday or weekday, greg_month or monthgreg_year or yearCalculate something like last Monday of January
last_day_of_the_week_in_month lwdm(Monday,Jan);
date d = lwdm.get_date(2002);//2002-Jan-28
first_day_of_the_week_in_monthgreg_weekday or weekday, greg_month or monthgreg_year or yearCalculate something like first Monday of January
first_day_of_the_week_in_month fdm(Monday,Jan);
date d = fdm.get_date(2002);//2002-Jan-07
partial_dategreg_day, greg_month or monthgreg_yearGenerates a date by applying the year to the given month and day.
partial_date pd(1,Jan);
date d = pd.get_date(2002);//2002-Jan-01
first_day_of_the_week_after greg_weekday or weekdaydateCalculate something like First Sunday after Jan 1,2002
first_day_of_the_week_after fdaf(Monday);
date d = fdaf.get_date(date(2002,Jan,1));//2002-Jan-07
first_day_of_the_week_before greg_weekday or weekdaydateCalculate something like First Monday before Feb 1,2002
first_day_of_the_week_before fdbf(Monday);
date d = fdbf.get_date(date(2002,Feb,1));//2002-Jan-28
Function OverviewFunction OverviewFunction PrototypeDescriptionExampledays days_until_weekday (const date&, const greg_weekday&) Calculates the number of days from given date until given weekday.
date d(2004,Jun,1); // Tuesday
greg_weekday gw(Friday);
days_until_weekday(d, gw); // 3 days
days days_before_weekday (const date&, const greg_weekday&) Calculates the number of day from given date to previous given weekday.
date d(2004,Jun,1); // Tuesday
greg_weekday gw(Friday);
days_before_weekday(d, gw); // 4 days
date next_weekday (const date&, const greg_weekday&) Generates a date object representing the date of the following weekday from the given date.
date d(2004,Jun,1); // Tuesday
greg_weekday gw(Friday);
next_weekday(d, gw); // 2004-Jun-4
date previous_weekday (const date&, const greg_weekday&) Generates a date object representing the date of the previous weekday from the given date.
date d(2004,Jun,1); // Tuesday
greg_weekday gw(Friday);
previous_weekday(d, gw); // 2004-May-28
topGregorian CalendarIntroduction --
Header --
FunctionsIntroductionIntroduction
The class boost::gregorian::gregorian_calendar implements the functions necessary to create the gregorian date system. It converts to the year-month-day form of a date to a day number representation and back.
For most purposes this class is simply accessed by gregorian::date and is not used directly by the user. However, there are useful functions that might be of use such as the end_of_month_day function.
The print month example demonstrates this.
HeaderHeader
#include "boost/date_time/gregorian/gregorian.hpp" //include all types plus i/o
or
#include "boost/date_time/gregorian/gregorian_types.hpp" //no i/o just types
FunctionsFunctionsSyntaxDescriptionExamplestatic short day_of_week(ymd_type)Return the day of the week (0==Sunday, 1==Monday, etc)See also gregorian::date day_of_weekstatic date_int_type day_number(ymd_type) Convert a ymd_type into a day number. The day number is an absolute number of days since the epoch start. static short end_of_month_day(year_type, month_type)Given a year and month determine the last day of the month. static ymd_type from_day_number(date_int_type) Convert a day number to a ymd struct. static bool is_leap_year(year_type)Returns true if specified year is a leap year.gregorian_calendar::is_leap_year(2000) --> truetopClass day_clockClass day_clocktopPosix TimePosix TimePosix Time SystemPosix Time SystemIntroduction --
Usage ExamplesIntroductionIntroduction
Defines a non-adjusted time system with nano-second/micro-second resolution and stable calculation properties. The nano-second resolution option uses 96 bits of underlying storage for each ptime while the micro-second resolution uses 64 bits per ptime (see Build Options for details). This time system uses the Gregorian calendar to implement the date portion of the time representation.
Usage ExamplesUsage ExamplesExampleDescriptionTime MathA few simple calculations using ptime and time_durations.Print HoursRetrieve time from clock, use a time_iterator.Local to UTC ConversionDemonstrates a couple different ways to convert a local to UTC time including daylight savings rules.Time PeriodsSome simple examples of intersection and display of time periods.Ptime ClassIntroduction --
Header --
Construction --
Construct from String --
Construct from Clock --
Construct using Conversion functions --
Accessors --
Conversion To String --
OperatorsIntroductionIntroduction
The class boost::posix_time::ptime is the primary interface for time point manipulation. In general, the ptime class is immutable once constructed although it does allow assignment.
Class ptime is dependent on gregorian::date for the interface to the date portion of a time point.
Other techniques for creating times include time iterators.
HeaderHeader
#include "boost/date_time/posix_time/posix_time.hpp" //include all types plus i/o
or
#include "boost/date_time/posix_time/posix_time_types.hpp" //no i/o just types
ConstructionConstructionSyntaxDescriptionExampleptime(date,time_duration)Construct from a date and offset
ptime t1(date(2002,Jan,10), time_duration(1,2,3));
ptime t2(date(2002,Jan,10), hours(1)+nanosec(5));
ptime(ptime)Copy constructorptime t3(t1)ptime(special_values sv)Constructor for infinities, not-a-date-time, max_date_time, and min_date_time
ptime d1(neg_infin);
ptime d2(pos_infin);
ptime d3(not_a_date_time);
ptime d4(max_date_time);
ptime d5(min_date_time);ptime;Default constructor. Creates a ptime object initialized to not_a_date_time. NOTE: this constructor can be disabled by defining DATE_TIME_NO_DEFAULT_CONSTRUCTOR (see compiler_config.hpp)ptime p; // p => not_a_date_timeConstruct from StringConstruct from StringSyntaxDescriptionExampleptime time_from_string(const std::string&)From delimited string.std::string ts("2002-01-20 23:59:59.000");
ptime t(time_from_string(ts))ptime from_iso_string(const std::string&)From non delimited iso form string.std::string ts("20020131T235959");
ptime t(from_iso_string(ts))Construct from ClockConstruct from ClockSyntaxDescriptionExamplestatic ptime second_clock::local_time();Get the local time, second level resolution, based on the time zone settings of the computer.ptime t(second_clock::local_time())static ptime second_clock::universal_time()Get the UTC time.ptime t(second_clock::universal_day())static ptime microsec_clock::local_time()Get the local time using a subsecond resolution clock. On Unix systems this is implemented using GetTimeOfDay. On most Win32 platforms it is implemented using ftime. Win32 systems often do not achieve microsecond resolution via this API. If higher resolution is critical to your application test your platform to see the acheived resolution.ptime t(microsec_clock::local_time())Construct using Conversion FunctionsConstruct using Conversion FunctionsSyntaxDescriptionExampleptime from_time_t(time_t t);Converts a time_t into a ptime.ptime t = from_time_t(tt);ptime from_ftime<ptime>(FILETIME ft);Creates a ptime object from a FILETIME structure.ptime t = from_ftime<ptime>(ft);AccessorsAccessorsSyntaxDescriptionExampledate date() constGet the date part of a time.
date d(2002,Jan,10);
ptime t(d, hour(1));
t.date() --> 2002-Jan-10;
time_duration time_of_day() constGet the time offset in the day.
date d(2002,Jan,10);
ptime t(d, hour(1));
t.time_of_day() --> 01:00:00;
Conversion to StringConversion to StringSyntaxDescriptionExamplestd::string to_simple_string(ptime)To YYYY-mmm-DD HH:MM:SS.fffffffff string where mmm 3 char month name. Fractional seconds only included if non-zero.2002-Jan-01 10:00:01.123456789std::string to_iso_string(ptime)Convert to form YYYYMMDDTHHMMSS,fffffffff where T is the date-time separator20020131T100001,123456789std::string to_iso_extended_string(ptime)Convert to form YYYY-MM-DDTHH:MM:SS,fffffffff where T is the date-time separator2002-01-31T10:00:01,123456789OperatorsOperatorsSyntaxDescriptionExample
operator==, operator!=,
operator>, operator<
operator>=, operator<=
A full complement of comparison operatorst1 == t2, etcptime operator+(date_duration) constReturn a ptime adding a day offset
date d(2002,Jan,1);
ptime t(d,minutes(5));
date_duration dd(1);
ptime t2 = t + dd;
ptime operator-(date_duration) constReturn a ptime subtracting a day offset
date d(2002,Jan,1);
ptime t(d,minutes(5));
date_duration dd(1);
ptime t2 = t - dd;
ptime operator+(time_duration) constReturn a ptime adding a time duration
date d(2002,Jan,1);
ptime t(d,minutes(5));
ptime t2 = t + hours(1) + minutes(2);
ptime operator-(time_duration) constReturn a ptime subtracting a time duration
date d(2002,Jan,1);
ptime t(d,minutes(5));
ptime t2 = t - minutes(2);
time_duration operator-(ptime) constTake the difference between two times.
date d(2002,Jan,1);
ptime t1(d,minutes(5));
ptime t2(d,seconds(5));
time_duration t3 = t2 - t1;//negative result
topTime DurationIntroduction --
Header --
Construction --
Count Based Construction --
Construct from String --
Accessors --
Conversion To String --
OperatorsIntroductionIntroduction
The class boost::posix_time::time_duration the base type responsible for representing a length of time. A duration can be either positive or negative. The general time_duration class provides a constructor that takes a count of the number of hours, minutes, seconds, and fractional seconds count as shown in the code fragment below. The resolution of the time_duration is configureable at compile time. See Build-Compiler Information for more information.
using namespace boost::posix_time;
time_duration td(1,2,3,4); //01:02:03.000000004 when resolution is nano seconds
time_duration td(1,2,3,4); //01:02:03.000004 when resolution is micro seconds
Several small helper classes that derive from a base time_duration, as shown below, to adjust for different resolutions. These classes can shorten code and make the intent clearer.
As an example:
using namespace boost::posix_time;
time_duration td = hours(1) + seconds(10); //01:00:01
td = hours(1) + nanosec(5); //01:00:00.000000005
Note that the existence of the higher resolution classes (eg: nanosec) depends on the installation of the library. See Build-Compiler Information for more information.
HeaderHeader
#include "boost/date_time/posix_time/posix_time.hpp" //include all types plus i/o
or
#include "boost/date_time/posix_time/posix_time_types.hpp" //no i/o just types
ConstructionConstructionSyntaxDescriptionExampletime_duration(hours,minutes,seconds,fractional_seconds)Construct ad duration from the countstime_duration td(1,2,3,9); //1 hr 2 min 3 sec 9 nanosecondsCount Based ConstructionCount Based ConstructionSyntaxDescriptionExamplehours(long)Number of hourstime_duration td = hours(3);minutes(long)Number of minutestime_duration td = minutes(3);seconds(long) Number of secondstime_duration td = seconds(3);millisec(long)Number of milliseconds.time_duration td = millisec(3);microsec(long)Number of microseconds.time_duration td = microsec(3);nanosec(long)Number of nanoseconds.time_duration td = nanosec(3);Construct from StringConstruct from StringSyntaxDescriptionExampletime_duration duration_from_string(const std::string&)From delimited string.
std::string ts("23:59:59.000");
time_duration td(duration_from_string(ts))
AccessorsAccessorsSyntaxDescriptionExamplelong hours() constGet the number of normalized hours.time_duration td(1,2,3); td.hours() --> 1long minutes() constGet the number of minutes normalized (0..59).time_duration td(1,2,3); td.minutes() --> 2long seconds() constGet the normalized number of second (0..59).time_duration td(1,2,3); td.seconds() --> 3long total_seconds() constGet the total number of seconds truncating any fractional seconds.
time_duration td(1,2,3,10);
td.total_seconds() --> (1*3600) + (2*60) + 3 == 3723
long fractional_seconds() constGet the number of fractional seconds.time_duration td(1,2,3, 1000); td.fractional_seconds() --> 1000bool is_negative() constTrue if duration is negative.time_duration td(-1,0,0); td.is_negative() --> truetime_duration invert_sign() constGenerate a new duration with the sign inverted/time_duration td(-1,0,0); td.invert_sign() --> 01:00:00static boost::date_time::time_resolutions resolution()Describes the resolution capability of the time_duration class. time_resolutions is an enum of resolution possibilities ranging from seconds to nanoseconds.time_duration::resolution() --> nanostatic time_duration::num_fractional_digits()Returns an unsigned short holding the number of fractional digits the time resolution has.time_duration::num_fractional_digits(); // 9 for nano, 6 for micro, etc.boost::int64_t ticks()Return the raw count of the duration type.time_duration td(0,0,0, 1000); td.ticks() --> 1000static time_duration unit()Return smallest possible unit of duration type (1 nanosecond).time_duration::unit() --> time_duration(0,0,0,1)Conversion To StringConversion To StringSyntaxDescriptionExamplestd::string to_simple_string(time_duration)To HH:MM:SS.fffffffff were fff is fractional seconds that are only included if non-zero.10:00:01.123456789std::string to_iso_string(time_duration)Convert to form HHMMSS,fffffffff.100001,123456789OperatorsOperatorsSyntaxDescriptionExample
operator==, operator!=,
operator>, operator<
operator>=, operator<=
A full complement of comparison operatorsdd1 == dd2, etctime_duration operator+(time_duration) constAdd durations.
time_duration td1(hours(1)+minutes(2));
time_duration td2(seconds(10));
time_duration td3 = td1 + td2;
time_duration operator-(time_duration) constSubtract durations.
time_duration td1(hours(1)+nanosec(2));
time_duration td2 = td1 - minutes(1);
time_duration operator/(int) constDivide the length of a duration by an integer value. Discards any remainder.
hours(3)/2 == time_duration(1,30,0);
nanosec(3)/2 == nanosec(1)
time_duration operator*(int) constMultiply the length of a duration by an integer value.hours(3)*2 == hours(6);topTime PeriodIntroduction --
Header --
Construction --
Accessors --
Conversion To String --
OperatorsIntroductionIntroduction
The class boost::posix_time::time_period provides direct representation for ranges between two times. Periods provide the ability to simplify some types of calculations by simplifying the conditional logic of the program.
The time periods example provides an example of using time periods.
HeaderHeader
#include "boost/date_time/posix_time/posix_time.hpp" //include all types plus i/o
or
#include "boost/date_time/posix_time/posix_time_types.hpp" //no i/o just types
ConstructionConstructionSyntaxDescriptionExampletime_period(ptime begin, ptime end) Create a period as [begin, end). If last is <= begin then the period will be defined as null.
date d(2002,Jan,01);
ptime t(d, seconds(10)); //10 sec after midnight
time_period tp(t, hours(3));
time_period(ptime start, time_duration len) Create a period as [begin, begin+len). If len is <= zero then the period will be defined as null.
date d(2002,Jan,01);
ptime t1(d, seconds(10)); //10 sec after midnight
ptime t2(d, hours(10)); //10 hours after midnight
time_period tp(t1, t2);
time_period(time_period rhs) Copy constructortime_period tp1(tp)AccessorsAccessorsSyntaxDescriptionExampleptime begin() constReturn first time of period.
date d(2002,Jan,01);
ptime t1(d, seconds(10)); //10 sec after midnight
ptime t2(d, hours(10)); //10 hours after midnight
time_period tp(t1, t2); tp.begin() --> 2002-Jan-01 00:00:10
ptime last() constReturn last time in the period
date d(2002,Jan,01);
ptime t1(d, seconds(10)); //10 sec after midnight
ptime t2(d, hours(10)); //10 hours after midnight
time_period tp(t1, t2); tp.last() --> 2002-Jan-01 09:59:59.999999999
ptime end() const Return one past the last in period
date d(2002,Jan,01);
ptime t1(d, seconds(10)); //10 sec after midnight
ptime t2(d, hours(10)); //10 hours after midnight
time_period tp(t1, t2); tp.last() --> 2002-Jan-01 10:00:00
time_duration length() constReturn the length of the time period.
date d(2002,Jan,01);
ptime t1(d); //midnight
time_period tp(t1, hours(1));
tp.length() --> 1 hour
bool is_null() constTrue if period is not well formed. eg: start less than end bool contains(ptime) constTrue if ptime is within the period
date d(2002,Jan,01);
ptime t1(d, seconds(10)); //10 sec after midnight
ptime t2(d, hours(10)); //10 hours after midnight
ptime t3(d, hours(2)); //2 hours after midnight
time_period tp(t1, t2); tp.contains(t3) --> true
bool contains(time_period) constTrue if period is within the period
time_period tp1(ptime(d,hours(1)), ptime(d,hours(12)));
time_period tp2(ptime(d,hours(2)), ptime(d,hours(4)));
tp1.contains(tp2) --> true
tp2.contains(tp1) --> false
bool intersects(time_period) const True if periods overlap
time_period tp1(ptime(d,hours(1)), ptime(d,hours(12)));
time_period tp2(ptime(d,hours(2)), ptime(d,hours(4)));
tp2.intersects(tp1) --> true
time_period intersection(time_period) constCalculate the intersection of 2 periods. Null if no intersection. time_period merge(time_period) constReturns union of two periods. Null if no intersection. time_period span(time_period) constCombines two periods and any gap between them such that start = min(p1.start, p2.start) and end = max(p1.end , p2.end). time_period shift(date_duration)Add duration to both start and end. Conversion To StringConversion To StringSyntaxDescriptionExamplestd::string to_simple_string(time_period dp)To [YYYY-mmm-DD hh:mm:ss.fffffffff/YYYY-mmm-DD hh:mm:ss.fffffffff] string where mmm is 3 char month name.[2002-Jan-01 01:25:10.000000001/2002-Jan-31 01:25:10.123456789]OperatorsOperatorsSyntaxDescriptionExampleoperator<<Output streaming operator for time duration. Uses facet to output [date time_of_day/date time_of_day]. The default is format is [YYYY-mmm-DD hh:mm:ss.fffffffff/YYYY-mmm-DD hh:mm:ss.fffffffff] string where mmm is 3 char month name.[2002-Jan-01 01:25:10.000000001/2002-Jan-31 01:25:10.123456789]operator==, operator!=Equality operators. Periods are equal if p1.begin == p2.begin && p1.last == p2.lastif (tp1 == tp2) {...operator<Ordering with no overlap. True if tp1.end() less than tp2.begin()if (tp1 < tp2) {...operator>Ordering with no overlap. True if tp1.begin() greater than tp2.end()if (tp1 > tp2) {... etcoperator<=, operator>=Defined in terms of the other operators. topTime IteratorsIntroduction --
Header --
Overview --
OperatorsIntroductionIntroduction
Time iterators provide a mechanism for iteration through times. Time iterators are similar to Bidirectional Iterators. However, time_iterators are different than standard iterators in that there is no underlying sequence, just a calculation function. In addition, time_iterators are directly comparable against instances of class ptime. Thus a second iterator for the end point of the iteration is not required, but rather a point in time can be used directly. For example, the following code iterates using a 15 minute iteration interval. The print hours example also illustrates the use of the time_iterator.
#include "boost/date_time/posix_time/posix_time.hpp"
#include <iostream>
int
main()
{
using namespace boost::gregorian;
using namespace boost::posix_time;
date d(2000,Jan,20);
ptime start(d);
ptime end = start + hours(1);
time_iterator titr(start,minutes(15)); //increment by 15 minutes
//produces 00:00:00, 00:15:00, 00:30:00, 00:45:00
while (titr < end) {
std::cout << to_simple_string(*titr) << std::endl;
++titr;
}
std::cout << "Now backward" << std::endl;
//produces 01:00:00, 00:45:00, 00:30:00, 00:15:00
while (titr > start) {
std::cout << to_simple_string(*titr) << std::endl;
--titr;
}
}
HeaderHeader
#include "boost/date_time/posix_time/posix_time.hpp" //include all types plus i/o
or
#include "boost/date_time/posix_time/posix_time_types.hpp" //no i/o just types
OverviewOverviewClassConstruction ParametersDescriptiontime_iteratorptime start_time, time_duration incrementIterate incrementing by the specified duration.OperatorsOperatorsSyntaxDescriptionExample
operator==(const ptime& rhs),
operator!=(const ptime& rhs),
operator>, operator<
operator>=, operator<=
A full complement of comparison operators
date d(2002,Jan,1);
ptime start_time(d, hours(1));
//increment by 10 minutes
time_iterator titr(start_time, minutes(10));
ptime end_time = start_time + hours(2);
if (titr == end_time) // false
if (titr != end_time) // true
if (titr >= end_time) // false
if (titr <= end_time) // true
prefix incrementIncrement the iterator by the specified duration.
//increment by 10 milli seconds
time_iterator titr(start_time, milliseconds(10));
++titr; // == start_time + 10 milliseconds
prefix decrementDecrement the iterator by the specified time duration.Example time_iterator titr(start_time, time_duration(1,2,3));
--titr; // == start_time - 1 hour, 2 minutes, and 3 secondstopLocal Time AdjustmentIntroduction --
Header --
OverviewIntroductionIntroduction
A frequent problem in time representation is the conversion between various local time systems. In general this is accomplished by using a reference time system. The reference time system is typically UTC.
Since the posix_time system does no internal time adjustment it can be used to represent both local times and UTC times. However, the user is currently left to handle conversions and time zone knowledge explicitly.
The library offers two different ways to perform UTC to local conversions. The first is using the time zone settings of the computer. This is a useful solution for converting a UTC time for a user machine. This approach depends on the ctime API and will provide incorrect results if the environment is set incorrectly. The other approach allows conversion from any zone to UTC and back independent of the settings of the time zone settings of the computer. The local utc conversion example demonstrates both of these techniques.
HeaderHeader
#include "boost/date_time/gregorian/gregorian.hpp" //include all types plus i/o
or
#include "boost/date_time/gregorian/gregorian_types.hpp" //no i/o just types
OverviewOverviewClassDescriptionExampledate_time::c_local_adjustor<ptime>::utc_to_local(ptime)Calculate local machine time from a UTC time based on time zone settings and the C API.
typedef boost::date_time::c_local_adjustor<ptime> local_adj;
ptime t10(date(2002,Jan,1), hours(7));
ptime t11 = local_adj::utc_to_local(t10);
date_time::local_adjustor<ptime, utc_offset, dst_rules>::utc_to_local(ptime)Calculate local machine time from a UTC time based daylight savings rules and utc offsetexampledate_time::local_adjustor<ptime, utc_offset, dst_rules>::local_to_utc(ptime)Calculate UTC time based on daylight savings rules and utc offset.exampletopDetailsDetailsCalculationsTimepoints --
Durations --
Intervals (Periods) --
Special Value HandlingTimepointsTimepoints
This section describes some of basic arithmetic rules that can be performed with timepoints. In general, Timepoints support basic arithmetic in conjunction with Durations as follows:
Timepoint + Duration --> Timepoint
Timepoint - Duration --> Timepoint
Timepoint - Timepoint --> Duration
Unlike regular numeric types, the following operations are undefined:
Duration + Timepoint --> Undefined
Duration - Timepoint --> Undefined
Timepoint + Timepoint --> Undefined
DurationsDurations
Durations represent a length of time and can have positive and negative values. It is frequently useful to be able to perform calculations with other durations and with simple integral values. The following describes these calculations:
Duration + Duration --> Duration
Duration - Duration --> Duration
Duration * Integer --> Duration
Integer * Duration --> Duration
Duration / Integer --> Duration (Integer Division rules)
Intervals (Periods)Intervals (Periods)
Interval logic is extremely useful for simplifying many 'calculations' for dates and times. The following describes the operations provided by periods which are based on half-open range. The following operations calculate new time periods based on two input time periods:
Timeperiod intersection Timeperiod --> Timeperiod (null interval if no intersection)
Timeperiod merge Timeperiod --> Timeperiod (null interval if no intersection)
Timeperiod shift Duration --> Timeperiod (shift start and end by duration amount)
In addition, periods support various queries that calculate boolean results. The first set is caluculations with other time periods:
Timeperiod == Timeperiod --> bool
Timeperiod < Timeperiod --> bool (true if lhs.last <= rhs.begin)
Timeperiod intersects Timeperiod --> bool
Timeperiod contains Timeperiod --> bool
Timeperiod is_adjacent Timeperiod --> bool
The following calculations are performed versus the Timepoint.
Timeperiod contains Timepoint --> bool
Timeperiod is_before Timepoint --> bool
Timeperiod is_after Timepoint --> bool
Special Value HandlingSpecial Value Handling
For many temporal problems it is useful for Duration and Timepoint types to support special values such as Not A Date Time (NADT) and infinity. In general special values such as Not A Date Time (NADT) and infinity should follow rules like floating point values. Note that it should be possible to configure NADT based systems to throw an exception instead of result in NADT.
Timepoint(NADT) + Duration --> Timepoint(NADT)
Timepoint(∞) + Duration --> Timepoint(∞)
Timepoint + Duration(∞) --> Timepoint(∞)
Timepoint - Duration(∞) --> Timepoint(-∞)
When performing operations on both positive and negative infinities, the library will produce results consistent with the following.
Timepoint(+∞) + Duration(-∞) --> NADT
Duration(+∞) + Duration(-∞) --> NADT
Duration(±∞) * Zero --> NADT
Duration(∞) * Integer(Not Zero) --> Duration(∞)
Duration(+∞) * -Integer --> Duration(-∞)
Duration(∞) / Integer --> Duration(∞)
Design GoalsCategoryDescriptionFunctionsInterfacesProvide concrete classes for manipulation of dates and times•
date, time, date_duration, time_duration, date_period, time_period, etc
•
support for infinity - positive infinity, negative infinity
•
iterators over time and date ranges
•
allow date and time implementations to be separate as much as possible
CalculationProvide a basis for performing efficient time calculations •days between dates •durations of times •durations of dates and times together Representation FlexibilityProvide the maximum possible reusability and flexibility•
traits based customization of internal
representations for size versus resolution control
•
Allowing the use of different epochs and resolution
(eg: seconds versus microseconds, dates starting at the
year 2000 versus dates starting in 1700)
•
Options for configuring unique calendar representations
(Gregorian + others)
•
the use of Julian Day number and the conversion between
this and the Gregorian/Julian calendar date
•Allow for flexible adjustments including
leap seconds
Date CalculationsProvide tools for date calculations•provide basis for calculation of complex event specs like holidays•calendar to calendar conversions•provide for ability to extend to new calendar systemsTime CalculationsProvide concrete classes for manipulation of time•provide the ability to handle cross time-zone issues•provide adjustments for daylight savings time (summer time)Clock InterfacesProvide classes for retrieving time current time•access to a network / high resolution time sources •retrieving the current date time information to populate classes I/O InterfacesProvide input and output for time including•multi-lingual support •provide ISO8601 compliant time facet •use I/O facets for different local behavior Tradeoffs: Stability, Predictability, and Approximations
Unavoidable Trade-offs
Unavoidable Trade-offs
The library does its best to provide everything a user could want, but there are certain inherent constraints that limit what any temporal library can do. Specifically, a user must choose which two of the following three capabilities are desired in any particular application:
•exact agreement with wall-clock time•accurate math, e.g. duration calculations•ability to handle timepoints in the future
Some libraries may implicitly promise to deliver all three, but if you actually put them to the test, only two can be true at once. This limitation is not a deficiency in the design or implementation of any particular library; rather it is a consequence of the way different time systems are defined by international standards. Let's look at each of the three cases:
If you want exact agreement with wall-clock time, you must use either UTC or local time. If you compute a duration by subtracting one UTC time from another and you want an answer accurate to the second, the two times must not be too far in the future because leap seconds affect the count but are only determined about 6 months in advance. With local times a future duration calculation could be off by an entire hour, since legislatures can and do change DST rules at will.
If you want to handle wall-clock times in the future, you won't be able (in the general case) to calculate exact durations, for the same reasons described above.
If you want accurate calculations with future times, you will have to use TAI or an equivalent, but the mapping from TAI to UTC or local time depends on leap seconds, so you will not have exact agreement with wall-clock time.
Stability, Predictability, and Approximations
Stability, Predictability, and Approximations
Here is some underlying theory that helps to explain what's going on. Remember that a temporal type, like any abstract data type (ADT), is a set of values together with operations on those values.
Stability
Stability
The representation of a type is stable if the bit pattern associated with a given value does not change over time. A type with an unstable representation is unlikely to be of much use to anyone, so we will insist that any temporal library use only stable representations.
An operation on a type is stable if the result of applying the operation to a particular operand(s) does not change over time.
Predictability
Predictability
Sets are most often classified into two categories: well-defined and ill-defined. Since a type is a set, we can extend these definitions to cover types. For any type T, there must be a predicate is_member( x ) which determines whether a value x is a member of type T. This predicate must return true, false, or dont_know.
If for all x, is_member( x ) returns either true or false, we say the set T is well-defined.
If for any x, is_member( x ) returns dont_know, we say the set T is ill-defined.
Those are the rules normally used in math. However, because of the special characteristics of temporal types, it is useful to refine this view and create a third category as follows:
For any temporal type T, there must be a predicate is_member( x, t ) which determines whether a value x is a member of T. The parameter t represents the time when the predicate is evaluated. For each xi, there must be a time ti and a value v such that:
•v = true or v = false, and•for all t < ti, is_member( xi, t ) returns dont_know, and•for all t >= ti, is_member( xi, t ) returns v.
ti is thus the time when we "find out" whether xi is a member of T. Now we can define three categories of temporal types:
If for all xi, ti = negative infinity, we say the type T is predictable.
If for some xi, ti = positive infinity, we say the type T is ill-formed.
Otherwise we say the type T is unpredictable (this implies that for some xi, ti is finite).
Ill-formed sets are not of much practical use, so we will not discuss them further. In plain english the above simply says that all the values of a predictable type are known ahead of time, but some values of an unpredictable type are not known until some particular time.
Stability of Operations
Stability of Operations
Predictable types have a couple of important properties:
•there is an order-preserving mapping from their elements onto a set of consecutive integers, and•duration operations on their values are stable
The practical effect of this is that duration calculations can be implemented with simple integer subtraction. Examples of predictable types are TAI timepoints and Gregorian dates.
Unpredictable types have exactly the opposite properties:
•there is no order-preserving mapping from their elements onto a set of consecutive integers, and•duration operations on their values are not stable.
Examples of unpredictable types are UTC timepoints and Local Time timepoints.
We can refine this a little by saying that a range within an unpredicatable type can be predictable, and operations performed entirely on values within that range will be stable. For example, the range of UTC timepoints from 1970-01-01 through the present is predictable, so calculations of durations within that range will be stable.
Approximations
Approximations
These limitations are problematical, because important temporal types like UTC and Local Time are in fact unpredictable, and therefore operations on them are sometimes unstable. Yet as a practical matter we often want to perform this kind of operation, such as computing the duration between two timepoints in the future that are specified in Local Time.
The best the library can do is to provide an approximation, which is generally possible and for most purposes will be good enough. Of course the documentation must specify when an answer will be approximate (and thus unstable) and how big the error may be. In many respects calculating with unpredictable sets is analogous to the use of floating point numbers, for which results are expected to only be approximately correct. Calculating with predictable sets would then be analogous to the user of integers, where results are expected to be exact.
For situations where exact answers are required or instability cannot be tolerated, the user must be able to specify this, and then the library should throw an exception if the user requests a computation for which an exact, stable answer is not possible.
Serialization
The boost::date_time library is compatible with the boost::serialization library's text and xml archives. The list of classes that are serializable are:
boost::gregorianboost::gregoriandatedate_durationdate_periodpartial_datenth_day_of_week_in_monthfirst_day_of_week_in_monthlast_day_of_week_in_monthfirst_day_of_week_beforefirst_day_of_week_aftergreg_monthgreg_daygreg_weekdayboost::posix_timeboost::posix_timeptimetime_durationtime_period
No extra steps are required to build the date_time library for serialization use.
Example text_archive usage:
using namespace boost::posix_time;
using namespace boost::gregorian;
ptime pt(date(2002, Feb, 14)), hours(10)), pt2(not_a_date_time);
std::ofstream ofs("tmp_file");
archive::test_oarchive oa(ofs);
oa << pt; // NOTE: no macro
ofs.close();
std::ifstream ifs("tmp_file");
archive::text_iarchive ia(ifs);
ia >> pt2; // NOTE: no macro
ifs.close();
pt == pt2; // true
Example xml_archive usage:
using namespace boost::gregorian;
date d(2002, Feb, 14), d2(not_a_date_time);
std::ofstream ofs("tmp_file");
archive::xml_oarchive oa(ofs);
oa << BOOST_SERIALIZATION_NVP(d); // macro required for xml_archive
ofs.close();
std::ifstream ifs("tmp_file");
archive::xml_iarchive ia(ifs);
ia >> BOOST_SERIALIZATION_NVP(d2); // macro required for xml_archive
ifs.close();
d == d2; // true
To use the date_time serialization code, the proper header files must be explicitly included. The header files are:
boost/date_time/gregorian/greg_serialize.hpp
and
boost/date_time/posix_time/time_serialize.hppTerminology
The following are a number of terms relevant to the date-time domain.
A taxonomy of temporal types:
•Timepoint -- Specifier for a location in the time continuum. Similar to a number on a ruler.•Timelength -- A duration of time unattached to any point on the time continuum.•Timeinterval -- A duration of time attached to a specific point in the time continuum.
And some other terms:
•Accuracy -- A measure of error, the difference between the reading of a clock and the true time.•Calendar System -- A system for labeling time points with day level resolution.•Clock Device -- A software component (tied to some hardware) that provides the current date or time with respect to a calendar or clock system.•Precision -- A measure of repeatability of a clock.•Resolution -- A specification of the smallest representable duration (eg: 1 second, 1 century) for a clock/calendar system or temporal type.•Stability -- The property of a class which says that the underlying representation (implementation) associated with a particular (abstract) value will never change.•Time System -- A system for labeling time points with higher resolution than day-level.
Some standard date-time terminology:
•Epoch -- Starting time point of a calendar or clock system.•DST -- Daylight savings time - a local time adjustment made in some regions during the summer to shift the clock time of the daylight hours•Time zone -- A region of the earth that provides for a 'local time' defined by DST rules and UT offset.•UTC Time -- Coordinated Universal Time - Civil time system as measured at longitude zero. Kept adjusted to earth rotation by use of leap seconds. Also known as Zulu Time. Replaced the similar system known as Greenwich Mean Time. For more see http://aa.usno.navy.mil/faq/docs/UT.html•TAI Time -- A high-accuracy monotonic (need better term) time system measured to .1 microsecond resolution by atomic clocks around the world. Not adjusted to earth rotation. For more see http://www.bipm.fr/enus/5_Scientific/c_time/time_server.html
Some more experimental ones:
•Local Time -- A time measured in a specific location of the universe.•Time Label -- A tuple that either completely or partially specifies a specific date-time with respect to a calendar or clock system. This is the year-month-day representation.•Adjusting Time Length -- A duration that represents varying physical durations depending on the moment in time. For example, a 1 month duration is typically not a fixed number of days and it depends on the date it is measured from to determine the actual length.
These are design sorts of terms:
•Generation function -- A function that generates a specific set of time points, lengths, or intervals based on one or more parameters. References•Date References•Time References•Other C/C++ Libraries•JAVA Date-Time Libraries•Scripting Language Libraries•Related Commercial and Fanciful Pages•Resolution, Precision, and AccuracyDate Calendar ReferencesDate Calendar References•ISO 8601 date time standard -- Summary by Markus Kuhn•Calendrical Calculations book by Reingold & Dershowitz•Calendar FAQ by Claus Tøndering•Calendar zone http://www.calendarzone.com•XML schema for date time•Will Linden's Calendar Links•XMAS calendar meltTimeTime•Martin Folwer on time patterns
•Recurring Events for Calendars•Patterns for things that Change with time•US National Institute of Standards and Technology Time Exhibits•Network Time Protocol at NTP.org•US Navy Systems of Time•International Atomic Time•Date-Time type PostgreSQL User Guide Other C/C++ LibrariesOther C/C++ Libraries•ctime C Standard library reference at cplusplus.com•XTime C extension proposal•Another C library extension proposal by David Tribble•libTAI is a C based time library•Time Zone Database C library for managing timezones/places•International Components for Unicode by IBM (open source)
•Calendar Class•Date Time Services•Time Zone Class•Date-Time Formatting•Julian Library in C by Mark Showalter -- NASAJAVA Date & Time Library Quick ReferenceJAVA Date & Time Library Quick Reference•Calendar class•Gregorian calendar•Date class•sql.time class•Date format symbols•Date format•Simple Date Format•Simple Time ZoneScripting Language LibrariesScripting Language Libraries•A python date library MX Date Time•Perl date-time
•Date-Time packages at CPAN•Date::Calc at CPAN•Date::Convert calendar conversions at CPAN•A PHP library Vlib Date LibraryRelated Commercial and Fanciful PagesRelated Commercial and Fanciful Pages•Leapsecond.com time page•World Time Server / TZ database•10000 year clock at Long Now Foundation•Timezones for PCsResolution, Precision, and AccuracyResolution, Precision, and Accuracy•Definitions with pictures from Agilent Technologies•Another set of pictures from Team Labs•Definitions from Southampton Institute•Definitions from Newport Corporation in the context of instrumentationBuild-Compiler InformationOverview --
Compilation Options --
Compiler/Portability Notes --
Directory Structure --
Required Boost LibrariesOverviewOverview
The library has several functions that require the creation of a library file. The Jamfile in the build directory will produce a "static" library (libboost_date_time) and a "dynamic/shared" library (boost_date_time) that contains these functions.
Compilation OptionsCompilation Options
By default the posix_time system uses a 64 bit integer and a 32 bit integer internally to provide nano-second level resolutions. As an alternative, a single 64 bit integer can be used to provide a microsecond level resolution. This alternative implementation may provide better performance and more compact memory usage for many applications that do not require nano-second resolutions.
To use the alternate resolution (64 bit microsecond) the variable BOOST_DATE_TIME_POSIX_TIME_STD_CONFIG must be defined in the library users project files (ie Makefile, Jamfile, etc). This macro is not used by the Gregorian system and therefore has no effect when building the library.
Compiler/Portability NotesCompiler/Portability Notes
The Boost Date-Time library has been built and tested with many compilers. However, some compilers and standard libraries have issues. While some of these issues can be worked around, others are difficult to work around. The following compilers fully support all aspects of the library:
•GCC 3.2-7 on Linux•GCC 2.95.3 with STLport-4.5.3 on Linux•GCC 3.1 (cygwin)•MSVC 7.1
In particular, a lack of support for standard locales limits the ability of the library to support iostream based input output. For these compilers a set of more limited string based input-output is provided. The compilers/standard libraries with this limitation include:
•GCC 2.9x on Linux•Borland 5.1.1 and 5.6•MSVC 6 SP5
Other compilers such as Comeau and Metroworks have been tested successfully with earlier versions of the library.
Directory StructureDirectory Structure
The directory tree has the following structure:
/boost/date_time -- common headers and template code
/boost/date_time/gregoran -- Gregorian calendar system header files
/boost/date_time/posix_time -- posix time system headers
/libs/date_time/build -- build files and output directory
/libs/date_time/test -- test battery for generic code
/libs/date_time/test/gregorian -- test battery for the Gregorian system
/libs/date_time/test/posix_time -- test battery for the posix_time system
/libs/date_time/examples/posix_time -- time example programs
/libs/date_time/examples/gregorian -- nifty example programs
/libs/date_time/src/gregorian -- cpp files for libboost_date_time
/libs/date_time/src/posix_time -- empty (one file, but no source code...)
Required Boost LibrariesRequired Boost Libraries
The library depends on
•boost.tokenizer•boost.integer(cstdint)•boost.operators•boost::lexical_cast
so at least these libraries need to be installed.
Tests
The library provides a large number of tests in the
libs/date_time/test
libs/date_time/test/gregorian
libs/date_time/test/posix_time
directories. Building and executing these tests assures that the installation is correct and that the library is functioning correctly. In addition, these tests facilitate the porting to new compilers. Finally, the tests provide examples of many functions not explicitly described in the usage examples.
Change HistoryChanges from Boost 1.31 to 1.32 (date_time 1.02 to 1.03)Changes from Boost 1.31 to 1.32 (date_time 1.02 to 1.03)TypeDescriptionBug FixSnap to end of month behavior corrected for year_functor. Previously, starting
from 2000-Feb-28 (leap year and not end of month) and iterating through the next
leap year would result in 2004-Feb-29 instead of 2004-Feb-28. This behavior has
been corrected to produce the correct result of 2004-Feb-28. Thanks to Bart Garst
for this change.
FeatureFree function for creating a ptime object from a FILETIME struct. This function
is only available on platforms that define BOOST_HAS_FTIME.
FeatureMicrosecond time clock is now available on most windows compilers as well as
Unix.
FeatureUse of the boost::serialization library is now available with most of the
date_time classes. Classes capable of serialization are: date_generator classes,
date, days, date_period, greg_month, greg_weekday, greg_day, ptime, time_duration,
and time_period. Thanks to Bart Garst for this change.
FeatureFunctions added to convert date and time classes to wstring. The library now
provides to_*_wstring as well as to_*_string functions for: simple, iso,
iso_extended, and sql for dates and compilers that support wstrings. Thanks to
Bart Garst for this change.
FeaturePeriod classes now handle zero length and NULL periods correctly. A NULL period
is a period with a negative length. Thanks to Frank Wolf and Bart Garst for this
change.
FeatureAdded end_of_month function to gregorian::date to return the last day of
the current month represented by the date. Result is undefined for
not_a_date_time or infinities.
Bug FixRemoved incorrect usage of BOOST_NO_CWCHAR macro throughout library.
FeatureNew names added for some date classes. Original names are still valid but may
some day be deprecated. Changes are:
date_durationis nowdaysnth_kday_of_monthis nownth_day_of_the_week_in_monthfirst_kday_of_monthis nowfirst_day_of_the_week_in_monthlast_kday_of_monthis nowlast_day_of_the_week_in_monthfirst_kday_afteris nowfirst_day_of_the_week_afterfirst_kday_beforeis nowfirst_day_of_the_week_beforeFeatureFree functions for date generators added. Functions are: days_until_weekday, days_before_weekday, next_weekday, and previous_weekday.
days days_until_weekday(date, greg_weekday);
days days_before_weekday(date, greg_weekday);
date next_weekday(date, greg_weekday);
date previous_weekday(date, greg_weekday);
Thanks to Bart Garst for this change.
FeatureNew experimental duration types added for months, years, and weeks. These classes
also provide mathematical operators for use with date and time classes. Be aware
that adding of months or years a time or date past the 28th of a month may show
non-normal mathematical properties. This is a result of 'end-of-month'
snapping used in the calculation. The last example below illustrates the
issue.
months m(12);
years y(1);
m == y; // true
days d(7);
weeks w(1);
d == w; // true
ptime t(...);
t += months(3);
date d(2004,Jan,30);
d += months(1); //2004-Feb-29
d -= months(1); //2004-Jan-29
Input streaming is not yet implemented for these types.
Thanks to Bart Garst for this change.
FeatureUnifying base class for date_generators brought in to gregorian namespace. See Print Holidays Example.
FeatureAdded constructors for date and ptime that allow for default construction (both)
and special values construction (ptime, both now support this). Default
constructors initialize the objects to not_a_date_time (NADT).
ptime p_nadt(not_a_date_time), p_posinf(pos_infin);
ptime p; // p == NADT
date d; // d == NADT
Thanks to Bart Garst for this change.
FeatureOutput streaming now supports wide stream output on compiler / standard library combinations that support wide streams. This allows code like:
std::wstringstream wss;
date d(2003,Aug,21);
wss << d;
Thanks to Bart Garst for this change.
FeatureInput streaming for date and time types is now supported on both wide and narrow streams:
date d(not_a_date_time);
std::stringstream ss("2000-FEB-29");
ss >> d; //Feb 29th, 2000
std::wstringstream ws("2000-FEB-29");
ws >> d; //Feb 29th, 2000
Thanks to Bart Garst for this change.
Bug Fix Fixed bug in duration_from_string() where a string formatted with
less than full amount of fractional digits created an incorrect
time_duration. With microsecond resolution for time durations
the string "1:01:01.010" created a time duration of
01:01:01.000010 instead of 01:01:01.010000
Bug FixFixed the special value constructor for gregorian::date and posix_time::ptime
when constructing with min_date_time or max_date_time. The wrong value was
constructed for these.
Changes from Boost 1.30 to 1.31 (date_time 1.01 to 1.02)Changes from Boost 1.30 to 1.31 (date_time 1.01 to 1.02)TypeDescriptionBug FixBuild configuration updated so dll, statically, and dynamically linkable library files are now produced with MSVC compilers. See Build/Compiler Information for more details.Bug FixTime_duration from_string is now correctly constructed from a negative value. (ie "-0:39:00.000") Code provided by Bart Garst.Bug FixFixed many MSVC compiler warnings when compiled with warning level 4.FeatureAdded prefix decrement operator (--) for date and time iterators. See Time Iterators and Date Iterators for more details. Code provided by Bart Garst.FeatureSpecial_values functionality added for date_duration, time_duration and time classes. Code provided by Bart Garst.Bug FixFixed time_duration_traits calculation bug which was causing time duration to be limited to 32bit range even when 64 bits were available. Thanks to Joe de Guzman for tracking this down.Bug FixProvided additional operators for duration types (eg: date_duration, time_duration). This includes dividable by integer and fixes to allow +=, -= operators. Thanks to Bart Garst for writing this code. Also, the documentation of Calculations has been improved.Bug FixAdded typedefs to boost::gregorian gregorian_types.hpp various date_generator function classes.FeatureAdded from_time_t function to convert time_t to a ptime.FeatureAdded a span function for combining periods. See date period and time period docs.FeatureAdded a function to time_duration to get the total number of seconds in a
duration truncating any fractional seconds. In addition, other resolutions
were added to allow for easy conversions. For example
seconds(1).total_milliseconds() == 1000
seconds(1).total_microseconds() == 1000000
hours(1).total_milliseconds() == 3600*1000 //3600 sec/hour
seconds(1).total_nanoseconds() == 1000000000
FeatureAdded output streaming operators for the date generator classes - partial_date, first_kday_after, first_kday_before, etc. Thanks to Bart Garst for this work.FeatureAdded unary- operators for durations for reversing the sign of a time duration. For example:
time_duration td(5,0,0); //5 hours
td = -td; //-5 hours
Thanks to Bart Garst for this work.FeatureAdded support for parsing strings with 'month names'. Thus creating a date object from string now accepts multiple formats ("2003-10-31","2003-Oct-31", and "2003-October-31"). Thus, date d = from_simple_string("2003-Feb-27") is now allowed. A bad month name string ( from_simple_string("2003-SomeBogusMonthName-27")) will cause a bad_month exception. On most compilers the string compare is case insensitive. Thanks to Bart Garst for this work.FeatureIn addition to support for month names or numbers, functions have been added to create date objects from multi-ordered date strings. Ex: "January-21-2002", "2002-Jan-21", and "21-Jan-2003". See Date Class for more details.Bug-FixVarious documentation fixes. Thanks to Bart Garst for updates.Changes from Boost 1.29 to 1.30 (date_time 1.00 to 1.01)Changes from Boost 1.29 to 1.30 (date_time 1.00 to 1.01)
Notice: The interface to the partial_date class (see date_algorithms) was changed. The order of construction parameters was changed which will cause some code to fail execution. This change was made to facilitate more generic local time adjustment code. Thus instead of specifying partial_date pd(Dec,25) the code needs to be changed to partial_date pd(25, Dec);
TypeDescriptionBug FixAdded new experimental feature for Daylight Savings Time calculations. This allows traits based specification of dst rules.FeatureAdded new interfaces to calculate julian day and modified julian day to the gregorian date class. See boost::gregorian::date.FeatureAdd new interface to calculate iso 8601 week number for a date. See boost::gregorian::date.FeatureAdd an iso 8601 time date-time format (eg: YYYYMMDDTHHHMMSS) parsing function. See Class ptime for more information.Feature Added a length function to the period template so that both date_periods and time_periods will now support this function.Bug FixSplit Jamfiles so that libs/date_time/build/Jamfile only builds library and /libs/date_time/libs/test/Jamfile which runs tests.Bug FixFixed many minor documentation issues.Bug FixRemoved the DATE_TIME_INLINE macro which was causing link errors. This macro is no longer needed in projects using the library.Bug FixAdded missing typedef for year_iterator to gregorian_types.hppBug FixFixed problem with gregorian ostream operators that prevented the use of wide streams.Bug-FixTighten error handling for dates so that date(2002, 2, 29) will throw a bad_day_of_month exception. Previously the date would be incorrectly constructed. Reported by sourceforge bug: 628054 among others.Acknowledgements
Many people have contributed to the development of this library. In particular Hugo Duncan and Joel de Guzman for help with porting to various compilers. For initial development of concepts and design Corwin Joy and Michael Kenniston deserve special thanks. Also extra thanks to Michael for writing up the theory and tradeoffs part of the documentation. Dave Zumbro for initial inspiration and sage thoughts. Many thanks to boost reviewers and users including: William Seymour, Kjell Elster, Beman Dawes, Gary Powell, Andrew Maclean, William Kempf, Peter Dimov, Chris Little, David Moore, Darin Adler, Gennadiy Rozental, Joachim Achtzehnter, Paul Bristow, Jan Langer, Mark Rodgers, Glen Knowles, Matthew Denman, and George Heintzelman.
ExamplesExamplesGeneral Usage Examples
The following provides some sample usage of dates.
See Date Programming
for more details.
using namespace boost::gregorian;
date weekstart(2002,Feb,1);
date weekend = weekstart + week(1);
date d2 = d1 + days(5);
date today = day_clock::local_day();
if (d2 >= today) {} //date comparison operators
date_period thisWeek(d1,d2);
if (thisWeek.contains(today)) {}//do something
//iterate and print the week
day_iterator itr(weekstart);
while (itr <= weekend) {
std::cout << (*itr) << std::endl;
++itr;
}
//input streaming
std::stringstream ss("2004-Jan-1");
ss >> d3;
//localized i/o using facets
std::locale global;
std::locale german(global,
new date_facet(de_short_month_names,
de_long_month_names,
de_special_value_names,
de_long_weekday_names,
de_long_weekday_names,
'.',
boost::date_time::ymd_order_dmy));
std::cout.imbue(global2);
date d4(2002, Oct, 1);
std::cout << d4; //01.Okt.2002
//date generator functions
date d5 = next_weekday(d4, Sunday); //calculate sunday following d4
//define a shorthand for the nth_day_of_the_week_in_month function object
typedef nth_day_of_the_week_in_month nth_dow;
//US labor day is first Monday in Sept
nth_dow labor_day(nth_dow::first,Monday, Sep);
date d6 = labor_day.get_date(2004); //calculate a specific date from functor
The following provides some example code using times.
See Time Programming
for more details.
use namespace boost::posix_time;
date d(2002,Feb,1); //an arbitrary date
ptime t1(d, hours(5)+nanosec(100)); //date + time of day offset
ptime t2 = t1 - minutes(4)+seconds(2);
ptime now = second_clock::local_time(); //use the clock
date today = now.date(); //Get the date part out of the time
date tommorrow = today + date_duration(1);
ptime tommorrow_start(tommorrow); //midnight
//input streaming
std::stringstream ss("2004-Jan-1 05:21:33.20");
ss >> t2;
//starting at current time iterator adds by one hour
time_iterator titr(now,hours(1));
for (; titr < tommorrow_start; ++titr) {
std::cout << (*titr) << std::endl;
}
topDates as Strings
Various parsing and output of strings.
/* The following is a simple example that shows conversion of dates
* to and from a std::string.
*
* Expected output:
* 2001-Oct-09
* 2001-10-09
* Tuesday October 9, 2001
* An expected exception is next:
* Exception: Month number is out of range 1..12
*/
#include "boost/date_time/gregorian/gregorian.hpp"
#include <iostream>
#include <string>
int
main()
{
using namespace boost::gregorian;
try {
// The following date is in ISO 8601 extended format (CCYY-MM-DD)
std::string s("2001-10-9"); //2001-October-09
date d(from_simple_string(s));
std::cout << to_simple_string(d) << std::endl;
//Read ISO Standard(CCYYMMDD) and output ISO Extended
std::string ud("20011009"); //2001-Oct-09
date d1(from_undelimited_string(ud));
std::cout << to_iso_extended_string(d1) << std::endl;
//Output the parts of the date - Tuesday October 9, 2001
date::ymd_type ymd = d1.year_month_day();
greg_weekday wd = d1.day_of_week();
std::cout << wd.as_long_string() << " "
<< ymd.month.as_long_string() << " "
<< ymd.day << ", " << ymd.year
<< std::endl;
//Let's send in month 25 by accident and create an exception
std::string bad_date("20012509"); //2001-??-09
std::cout << "An expected exception is next: " << std::endl;
date wont_construct(from_undelimited_string(bad_date));
//use wont_construct so compiler doesn't complain, but you wont get here!
std::cout << "oh oh, you shouldn't reach this line: "
<< to_iso_string(wont_construct) << std::endl;
}
catch(std::exception& e) {
std::cout << " Exception: " << e.what() << std::endl;
}
return 0;
}
topDays Alive
Calculate the number of days you have been living using durations and dates.
/* Short example that calculates the number of days since user was born.
* Demonstrates comparisons of durations, use of the day_clock,
* and parsing a date from a string.
*/
#include "boost/date_time/gregorian/gregorian.hpp"
#include <iostream>
int
main()
{
using namespace boost::gregorian;
std::string s;
std::cout << "Enter birth day YYYY-MM-DD (eg: 2002-02-01): ";
std::cin >> s;
try {
date birthday(from_simple_string(s));
date today = day_clock::local_day();
days days_alive = today - birthday;
days one_day(1);
if (days_alive == one_day) {
std::cout << "Born yesterday, very funny" << std::endl;
}
else if (days_alive < days(0)) {
std::cout << "Not born yet, hmm: " << days_alive.days()
<< " days" <<std::endl;
}
else {
std::cout << "Days alive: " << days_alive.days() << std::endl;
}
}
catch(...) {
std::cout << "Bad date entered: " << s << std::endl;
}
return 0;
}
topDays Between New Years
Calculate the number of days till new years
/* Provides a simple example of using a date_generator, and simple
* mathematical operatorations, to calculate the days since
* New Years day of this year, and days until next New Years day.
*
* Expected results:
* Adding together both durations will produce 366 (365 in a leap year).
*/
#include <iostream>
#include "boost/date_time/gregorian/gregorian.hpp"
int
main()
{
using namespace boost::gregorian;
date today = day_clock::local_day();
partial_date new_years_day(1,Jan);
//Subtract two dates to get a duration
days days_since_year_start = today - new_years_day.get_date(today.year());
std::cout << "Days since Jan 1: " << days_since_year_start.days()
<< std::endl;
days days_until_year_start = new_years_day.get_date(today.year()+1) - today;
std::cout << "Days until next Jan 1: " << days_until_year_start.days()
<< std::endl;
return 0;
};
topEnd of the Months
Iterates accross the remaining months in a given year, always landing on the last day of the month.
/* Simple program that uses the gregorian calendar to find the last
* day of the month and then display the last day of every month left
* in the year.
*/
#include "boost/date_time/gregorian/gregorian.hpp"
#include <iostream>
int
main()
{
using namespace boost::gregorian;
std::cout << " Enter Year(ex: 2002): ";
int year, month;
std::cin >> year;
std::cout << " Enter Month(1..12): ";
std::cin >> month;
try {
int day = gregorian_calendar::end_of_month_day(year,month);
date end_of_month(year,month,day);
//Iterate thru by months --
month_iterator mitr(end_of_month,1);
date start_of_next_year(year+1, Jan, 1);
//loop thru the days and print each one
while (mitr < start_of_next_year){
std::cout << to_simple_string(*mitr) << std::endl;
++mitr;
}
}
catch(...) {
std::cout << "Invalid Date Entered" << std::endl;
}
return 0;
}
topLocalization Demonstration
The boost::date_time library provides the ability to create customized locale facets. Date ordering, language, seperators, and abbreviations can be customized.
/* The following shows the creation of a facet for the output of
* dates in German (please forgive me for any errors in my German --
* I'm not a native speaker).
*/
#include "boost/date_time/gregorian/gregorian.hpp"
#include <iostream>
/* Define a series of char arrays for short and long name strings to be
* associated with date output. */
const char* const de_short_month_names[] =
{
"Jan", "Feb", "Mar", "Apr", "Mai", "Jun",
"Jul", "Aug", "Sep", "Okt", "Nov", "Dez", "NAM"
};
const char* const de_long_month_names[] =
{
"Januar", "Februar", "Marz", "April", "Mai",
"Juni", "Juli", "August", "September", "Oktober",
"November", "Dezember", "NichtDerMonat"
};
const char* const de_special_value_names[] =
{
"NichtDatumzeit", "-unbegrenztheit", "+unbegrenztheit"
};
const char* const de_long_weekday_names[] =
{
"Sonntag", "Montag", "Dienstag", "Mittwoch",
"Donnerstag", "Freitag", "Samstag"
};
const char* const de_short_weekday_names[] =
{
"Son", "Mon", "Die","Mit", "Don", "Fre", "Sam"
};
const char* const us_short_month_names[] =
{
"Jan", "Feb", "Mar", "Apr", "May", "Jun",
"Jul", "Aug", "Sep", "Oct", "Nov", "Dec", "NAD"
};
const char* const us_long_month_names[] =
{
"January", "February", "March", "April", "May",
"June", "July", "August", "September", "October",
"November", "December", "Not-A-Date"
};
const char* const us_special_value_names[] =
{
"Not-A-Date", "-infinity", "+infinity"
};
const char* const us_long_weekday_names[] =
{
"Sunday", "Monday", "Tuesday", "Wenesday",
"Thursday", "Friday", "Saturday"
};
const char* const us_short_weekday_names[] =
{
"Sun", "Mon", "Tue","Wed", "Thu", "Fri", "Sat"
};
int
main()
{
#ifndef BOOST_DATE_TIME_NO_LOCALE
using namespace boost::gregorian;
typedef boost::date_time::all_date_names_put<greg_facet_config> date_facet;
//create a new local
std::locale default_locale;
std::locale german_dates1(default_locale,
new date_facet(de_short_month_names,
de_long_month_names,
de_special_value_names,
de_short_weekday_names,
de_long_weekday_names,
'.',
boost::date_time::ymd_order_dmy,
boost::date_time::month_as_integer));
date d1(2002, Oct, 1);
std::cout.imbue(german_dates1);
// output the date in German using short month names
std::cout << d1 << std::endl; //01.10.2002
std::locale german_dates2(default_locale,
new date_facet(de_short_month_names,
de_long_month_names,
de_special_value_names,
de_short_weekday_names,
de_long_weekday_names,
'.',
boost::date_time::ymd_order_dmy,
boost::date_time::month_as_long_string));
std::cout.imbue(german_dates2);
greg_month m = d1.month();
std::cout << m << std::endl; //Oktober
greg_weekday wd = d1.day_of_week();
std::cout << wd << std::endl; //Dienstag
//Numeric date format with US month/day/year ordering
std::locale usa_dates1(default_locale,
new date_facet(us_short_month_names,
us_long_month_names,
us_special_value_names,
us_short_weekday_names,
us_long_weekday_names,
'/',
boost::date_time::ymd_order_us,
boost::date_time::month_as_integer));
std::cout.imbue(usa_dates1);
std::cout << d1 << std::endl; // 10/01/2002
//English names, iso order (year-month-day), '-' separator
std::locale usa_dates2(default_locale,
new date_facet(us_short_month_names,
us_long_month_names,
us_special_value_names,
us_short_weekday_names,
us_long_weekday_names,
'-',
boost::date_time::ymd_order_iso,
boost::date_time::month_as_short_string));
std::cout.imbue(usa_dates2);
std::cout << d1 << std::endl; // 2002-Oct-01
#else
std::cout << "Sorry, localization is not supported by this compiler/library"
<< std::endl;
#endif
return 0;
}
topDate Period Calculations
Calculates if a date is in an 'irregular' collection of periods using period calculation functions.
/*
This example demonstrates a simple use of periods for the calculation
of date information.
The example calculates if a given date is a weekend or holiday
given an exclusion set. That is, each weekend or holiday is
entered into the set as a time interval. Then if a given date
is contained within any of the intervals it is considered to
be within the exclusion set and hence is a offtime.
Output:
Number Excluded Periods: 5
20020202/20020203
20020209/20020210
20020212/20020212
20020216/20020217
In Exclusion Period: 20020216 --> 20020216/20020217
20020223/20020224
*/
#include "boost/date_time/gregorian/gregorian.hpp"
#include <set>
#include <algorithm>
#include <iostream>
typedef std::set<boost::gregorian::date_period> date_period_set;
//Simple population of the exclusion set
date_period_set
generateExclusion()
{
using namespace boost::gregorian;
date_period periods_array[] =
{ date_period(date(2002,Feb,2), date(2002,Feb,4)),//weekend of 2nd-3rd
date_period(date(2002,Feb,9), date(2002,Feb,11)),
date_period(date(2002,Feb,16), date(2002,Feb,18)),
date_period(date(2002,Feb,23), date(2002,Feb,25)),
date_period(date(2002,Feb,12), date(2002,Feb,13))//a random holiday 2-12
};
const int num_periods = sizeof(periods_array)/sizeof(date_period);
date_period_set ps;
//insert the periods in the set
std::insert_iterator<date_period_set> itr(ps, ps.begin());
std::copy(periods_array, periods_array+num_periods, itr );
return ps;
}
int main()
{
using namespace boost::gregorian;
date_period_set ps = generateExclusion();
std::cout << "Number Excluded Periods: " << ps.size() << std::endl;
date d(2002,Feb,16);
date_period_set::const_iterator i = ps.begin();
//print the periods, check for containment
for (;i != ps.end(); i++) {
std::cout << to_iso_string(*i) << std::endl;
//if date is in exclusion period then print it
if (i->contains(d)) {
std::cout << "In Exclusion Period: "
<< to_iso_string(d) << " --> " << to_iso_string(*i)
<< std::endl;
}
}
return 0;
}
topPrint Holidays
This is an example of using functors to define a holiday schedule
/* Generate a set of dates using a collection of date generators
* Output looks like:
* Enter Year: 2002
* 2002-Jan-01 [Tue]
* 2002-Jan-21 [Mon]
* 2002-Feb-12 [Tue]
* 2002-Jul-04 [Thu]
* 2002-Sep-02 [Mon]
* 2002-Nov-28 [Thu]
* 2002-Dec-25 [Wed]
* Number Holidays: 7
*/
#include "boost/date_time/gregorian/gregorian.hpp"
#include <algorithm>
#include <functional>
#include <vector>
#include <iostream>
#include <set>
void
print_date(boost::gregorian::date d)
{
using namespace boost::gregorian;
#if defined(BOOST_DATE_TIME_NO_LOCALE)
std::cout << to_simple_string(d) << " [" << d.day_of_week() << "]\n";
#else
std::cout << d << " [" << d.day_of_week() << "]\n";
#endif
}
int
main() {
std::cout << "Enter Year: ";
int year;
std::cin >> year;
using namespace boost::gregorian;
//define a collection of holidays fixed by month and day
std::vector<year_based_generator*> holidays;
holidays.push_back(new partial_date(1,Jan)); //Western New Year
holidays.push_back(new partial_date(4,Jul)); //US Independence Day
holidays.push_back(new partial_date(25, Dec));//Christmas day
//define a shorthand for the nth_day_of_the_week_in_month function object
typedef nth_day_of_the_week_in_month nth_dow;
//US labor day
holidays.push_back(new nth_dow(nth_dow::first, Monday, Sep));
//MLK Day
holidays.push_back(new nth_dow(nth_dow::third, Monday, Jan));
//Pres day
holidays.push_back(new nth_dow(nth_dow::second, Tuesday, Feb));
//Thanksgiving
holidays.push_back(new nth_dow(nth_dow::fourth, Thursday, Nov));
typedef std::set<date> date_set;
date_set all_holidays;
for(std::vector<year_based_generator*>::iterator it = holidays.begin();
it != holidays.end(); ++it)
{
all_holidays.insert((*it)->get_date(year));
}
//print the holidays to the screen
std::for_each(all_holidays.begin(), all_holidays.end(), print_date);
std::cout << "Number Holidays: " << all_holidays.size() << std::endl;
return 0;
}
topPrint Month
Simple utility to print out days of the month with the days of a month. Demontstrates date iteration (date_time::date_itr).
/* This example prints all the dates in a month. It demonstrates
* the use of iterators as well as functions of the gregorian_calendar
*
* Output:
* Enter Year: 2002
* Enter Month(1..12): 2
* 2002-Feb-01 [Fri]
* 2002-Feb-02 [Sat]
* 2002-Feb-03 [Sun]
* 2002-Feb-04 [Mon]
* 2002-Feb-05 [Tue]
* 2002-Feb-06 [Wed]
* 2002-Feb-07 [Thu]
*/
#include "boost/date_time/gregorian/gregorian.hpp"
#include <iostream>
int
main()
{
std::cout << "Enter Year: ";
int year, month;
std::cin >> year;
std::cout << "Enter Month(1..12): ";
std::cin >> month;
using namespace boost::gregorian;
try {
//Use the calendar to get the last day of the month
int eom_day = gregorian_calendar::end_of_month_day(year,month);
date endOfMonth(year,month,eom_day);
//construct an iterator starting with firt day of the month
day_iterator ditr(date(year,month,1));
//loop thru the days and print each one
for (; ditr <= endOfMonth; ++ditr) {
#if defined(BOOST_DATE_TIME_NO_LOCALE)
std::cout << to_simple_string(*ditr) << " ["
#else
std::cout << *ditr << " ["
#endif
<< ditr->day_of_week() << "]"
<< std::endl;
}
}
catch(std::exception& e) {
std::cout << "Error bad date, check your entry: \n"
<< " Details: " << e.what() << std::endl;
}
return 0;
}
topMonth Adding
Adding a month to a day without the use of iterators.
/* Simple program that uses the gregorian calendar to progress by exactly
* one month, irregardless of how many days are in that month.
*
* This method can be used as an alternative to iterators
*/
#include "boost/date_time/gregorian/gregorian.hpp"
#include <iostream>
int
main()
{
using namespace boost::gregorian;
typedef boost::date_time::month_functor<date> add_month;
date d = day_clock::local_day();
add_month mf(1);
date d2 = d + mf.get_offset(d);
std::cout << "Today is: " << to_simple_string(d) << ".\n"
<< "One month from today will be: " << to_simple_string(d2)
<< std::endl;
return 0;
}
topTime Math
Various types of calculations with times and time durations.
/* Some simple examples of constructing and calculating with times
* Output:
* 2002-Feb-01 00:00:00 - 2002-Feb-01 05:04:02.001000000 = -5:04:02.001000000
*/
#include "boost/date_time/posix_time/posix_time.hpp"
#include <iostream>
int
main()
{
using namespace boost::posix_time;
using namespace boost::gregorian;
date d(2002,Feb,1); //an arbitrary date
//construct a time by adding up some durations durations
ptime t1(d, hours(5)+minutes(4)+seconds(2)+millisec(1));
//construct a new time by subtracting some times
ptime t2 = t1 - hours(5)- minutes(4)- seconds(2)- millisec(1);
//construct a duration by taking the difference between times
time_duration td = t2 - t1;
std::cout << to_simple_string(t2) << " - "
<< to_simple_string(t1) << " = "
<< to_simple_string(td) << std::endl;
return 0;
}
topPrint Hours
Demonstrate time iteration, clock retrieval, and simple calculation.
/* Print the remaining hours of the day
* Uses the clock to get the local time
* Use an iterator to iterate over the remaining hours
* Retrieve the date part from a time
*
* Expected Output something like:
*
* 2002-Mar-08 16:30:59
* 2002-Mar-08 17:30:59
* 2002-Mar-08 18:30:59
* 2002-Mar-08 19:30:59
* 2002-Mar-08 20:30:59
* 2002-Mar-08 21:30:59
* 2002-Mar-08 22:30:59
* 2002-Mar-08 23:30:59
* Time left till midnight: 07:29:01
*/
#include "boost/date_time/posix_time/posix_time.hpp"
#include <iostream>
int
main()
{
using namespace boost::posix_time;
using namespace boost::gregorian;
//get the current time from the clock -- one second resolution
ptime now = second_clock::local_time();
//Get the date part out of the time
date today = now.date();
date tommorrow = today + days(1);
ptime tommorrow_start(tommorrow); //midnight
//iterator adds by one hour
time_iterator titr(now,hours(1));
for (; titr < tommorrow_start; ++titr) {
std::cout << to_simple_string(*titr) << std::endl;
}
time_duration remaining = tommorrow_start - now;
std::cout << "Time left till midnight: "
<< to_simple_string(remaining) << std::endl;
return 0;
}
topLocal to UTC Conversion
Demonstrate utc to local and local to utc calculations including dst.
/* Demonstrate conversions between a local time and utc
* Output:
*
* UTC <--> New York while DST is NOT active (5 hours)
* 2001-Dec-31 19:00:00 in New York is 2002-Jan-01 00:00:00 UTC time
* 2002-Jan-01 00:00:00 UTC is 2001-Dec-31 19:00:00 New York time
*
* UTC <--> New York while DST is active (4 hours)
* 2002-May-31 20:00:00 in New York is 2002-Jun-01 00:00:00 UTC time
* 2002-Jun-01 00:00:00 UTC is 2002-May-31 20:00:00 New York time
*
* UTC <--> Arizona (7 hours)
* 2002-May-31 17:00:00 in Arizona is 2002-Jun-01 00:00:00 UTC time
*/
#include "boost/date_time/posix_time/posix_time.hpp"
#include "boost/date_time/local_time_adjustor.hpp"
#include "boost/date_time/c_local_time_adjustor.hpp"
#include <iostream>
int
main()
{
using namespace boost::posix_time;
using namespace boost::gregorian;
//This local adjustor depends on the machine TZ settings-- highly dangerous!
typedef boost::date_time::c_local_adjustor<ptime> local_adj;
ptime t10(date(2002,Jan,1), hours(7));
ptime t11 = local_adj::utc_to_local(t10);
std::cout << "UTC <--> Zone base on TZ setting" << std::endl;
std::cout << to_simple_string(t11) << " in your TZ is "
<< to_simple_string(t10) << " UTC time "
<< std::endl;
time_duration td = t11 - t10;
std::cout << "A difference of: "
<< to_simple_string(td) << std::endl;
//eastern timezone is utc-5
typedef boost::date_time::local_adjustor<ptime, -5, us_dst> us_eastern;
ptime t1(date(2001,Dec,31), hours(19)); //5 hours b/f midnight NY time
std::cout << "\nUTC <--> New York while DST is NOT active (5 hours)"
<< std::endl;
ptime t2 = us_eastern::local_to_utc(t1);
std::cout << to_simple_string(t1) << " in New York is "
<< to_simple_string(t2) << " UTC time "
<< std::endl;
ptime t3 = us_eastern::utc_to_local(t2);//back should be the same
std::cout << to_simple_string(t2) << " UTC is "
<< to_simple_string(t3) << " New York time "
<< "\n\n";
ptime t4(date(2002,May,31), hours(20)); //4 hours b/f midnight NY time
std::cout << "UTC <--> New York while DST is active (4 hours)" << std::endl;
ptime t5 = us_eastern::local_to_utc(t4);
std::cout << to_simple_string(t4) << " in New York is "
<< to_simple_string(t5) << " UTC time "
<< std::endl;
ptime t6 = us_eastern::utc_to_local(t5);//back should be the same
std::cout << to_simple_string(t5) << " UTC is "
<< to_simple_string(t6) << " New York time "
<< "\n" << std::endl;
//Arizona timezone is utc-7 with no dst
typedef boost::date_time::local_adjustor<ptime, -7, no_dst> us_arizona;
ptime t7(date(2002,May,31), hours(17));
std::cout << "UTC <--> Arizona (7 hours)" << std::endl;
ptime t8 = us_arizona::local_to_utc(t7);
std::cout << to_simple_string(t7) << " in Arizona is "
<< to_simple_string(t8) << " UTC time "
<< std::endl;
return 0;
}
topTime Periods
Demonstrate some simple uses of time periods.
/* Some simple examples of constructing and calculating with times
* Returns:
* [2002-Feb-01 00:00:00/2002-Feb-01 23:59:59.999999999] contains 2002-Feb-01 03:00:05
* [2002-Feb-01 00:00:00/2002-Feb-01 23:59:59.999999999] intersected with
* [2002-Feb-01 00:00:00/2002-Feb-01 03:00:04.999999999] is
* [2002-Feb-01 00:00:00/2002-Feb-01 03:00:04.999999999]
*/
#include "boost/date_time/posix_time/posix_time.hpp"
#include <iostream>
using namespace boost::posix_time;
using namespace boost::gregorian;
//Create a simple period class to contain all the times in a day
class day_period : public time_period
{
public:
day_period(date d) : time_period(ptime(d),//midnight
ptime(d,hours(24)))
{}
};
int
main()
{
date d(2002,Feb,1); //an arbitrary date
//a period that represents a day
day_period dp(d);
ptime t(d, hours(3)+seconds(5)); //an arbitray time on that day
if (dp.contains(t)) {
std::cout << to_simple_string(dp) << " contains "
<< to_simple_string(t) << std::endl;
}
//a period that represents part of the day
time_period part_of_day(ptime(d, hours(0)), t);
//intersect the 2 periods and print the results
if (part_of_day.intersects(dp)) {
time_period result = part_of_day.intersection(dp);
std::cout << to_simple_string(dp) << " intersected with\n"
<< to_simple_string(part_of_day) << " is \n"
<< to_simple_string(result) << std::endl;
}
return 0;
}
topLibrary ReferenceLibrary Reference
The following is a detailed reference of the date_time library. A click on any of the reference links will take you to a list of the header files found in that section. Following one of those links will take you to a list of the items declared in that header file. Further sublinks take you to detailed descriptions of each individual item.
Date Time ReferenceHeader <boost/date_time/adjust_functors.hpp>namespace boost {
namespace date_time {
template<typename date_type> class day_functor;
template<typename date_type> class month_functor;
template<typename date_type> class week_functor;
template<typename date_type> class year_functor;
}
}Class template day_functorClass template day_functor -- Functor to iterate a fixed number of days. boost::date_time::day_functortemplate<typename date_type>
class day_functor {
public:
// types
typedef date_type::duration_type duration_type;
// construct/copy/destruct
day_functor(int);
// public member functions
duration_type get_offset(const date_type &) const;
duration_type get_neg_offset(const date_type &) const;
};DescriptionDescriptionday_functor construct/copy/destructday_functor construct/copy/destruct1.day_functor(int f);day_functor public member functionsday_functor public member functions1.duration_type get_offset(const date_type & d) const;2.duration_type get_neg_offset(const date_type & d) const;Class template month_functorClass template month_functor -- Provides calculation to find next nth month given a date. boost::date_time::month_functortemplate<typename date_type>
class month_functor {
public:
// types
typedef date_type::duration_type duration_type;
typedef date_type::calendar_type cal_type;
typedef cal_type::ymd_type ymd_type;
typedef cal_type::day_type day_type;
// construct/copy/destruct
month_functor(int);
// public member functions
duration_type get_offset(const date_type &) const;
duration_type get_neg_offset(const date_type &) const;
};DescriptionDescriptionThis adjustment function provides the logic for 'month-based' advancement on a ymd based calendar. The policy it uses to handle the non existant end of month days is to back up to the last day of the month. Also, if the starting date is the last day of a month, this functor will attempt to adjust to the end of the month. month_functor construct/copy/destructmonth_functor construct/copy/destruct1.month_functor(int f);month_functor public member functionsmonth_functor public member functions1.duration_type get_offset(const date_type & d) const;2.duration_type get_neg_offset(const date_type & d) const;Returns a negative duration_type. Class template week_functorClass template week_functor -- Functor to iterate a over weeks. boost::date_time::week_functortemplate<typename date_type>
class week_functor {
public:
// types
typedef date_type::duration_type duration_type;
typedef date_type::calendar_type calendar_type;
// construct/copy/destruct
week_functor(int);
// public member functions
duration_type get_offset(const date_type &) const;
duration_type get_neg_offset(const date_type &) const;
};DescriptionDescriptionweek_functor construct/copy/destructweek_functor construct/copy/destruct1.week_functor(int f);week_functor public member functionsweek_functor public member functions1.duration_type get_offset(const date_type & d) const;2.duration_type get_neg_offset(const date_type & d) const;Class template year_functorClass template year_functor -- Functor to iterate by a year adjusting for leap years. boost::date_time::year_functortemplate<typename date_type>
class year_functor {
public:
// types
typedef date_type::duration_type duration_type;
// construct/copy/destruct
year_functor(int);
// public member functions
duration_type get_offset(const date_type &) const;
duration_type get_neg_offset(const date_type &) const;
};DescriptionDescriptionyear_functor construct/copy/destructyear_functor construct/copy/destruct1.year_functor(int f);year_functor public member functionsyear_functor public member functions1.duration_type get_offset(const date_type & d) const;2.duration_type get_neg_offset(const date_type & d) const;Header <boost/date_time/c_local_time_adjustor.hpp>Time adjustment calculations based on machinenamespace boost {
namespace date_time {
template<typename time_type> class c_local_adjustor;
}
}Class template c_local_adjustorClass template c_local_adjustor -- Adjust to / from utc using the C API. boost::date_time::c_local_adjustortemplate<typename time_type>
class c_local_adjustor {
public:
// types
typedef time_type::time_duration_type time_duration_type;
typedef time_type::date_type date_type;
typedef date_type::duration_type date_duration_type;
// public static functions
time_type utc_to_local(const time_type &) ;
};DescriptionDescriptionWarning!!! This class assumes that timezone settings of the machine are correct. This can be a very dangerous assumption. c_local_adjustor public static functionsc_local_adjustor public static functions1.time_type utc_to_local(const time_type & t) ;Convert a utc time to local time. Header <boost/date_time/c_time.hpp>Provide workarounds related to the ctime headernamespace std {
}Header <boost/date_time/compiler_config.hpp>namespace std {
}Header <boost/date_time/constrained_value.hpp>namespace boost {
namespace CV {
template<typename value_policies> class constrained_value;
template<typename rep_type, rep_type min_value, rep_type max_value,
typename exception_type>
class simple_exception_policy;
// Represent a min or max violation type.
enum violation_enum { min_violation, max_violation };
}
}Class template constrained_valueClass template constrained_value -- A template to specify a constrained basic value type. boost::CV::constrained_valuetemplate<typename value_policies>
class constrained_value {
public:
// types
typedef value_policies::value_type value_type;
// construct/copy/destruct
constrained_value(value_type);
constrained_value& operator=(value_type);
// public member functions
operator value_type() const;
// public static functions
value_type max BOOST_PREVENT_MACRO_SUBSTITUTION() ;
value_type min BOOST_PREVENT_MACRO_SUBSTITUTION() ;
// private member functions
void assign(value_type) ;
};DescriptionDescriptionThis template provides a quick way to generate an integer type with a constrained range. The type provides for the ability to specify the min, max, and and error handling policy.value policies A class that provides the range limits via the min and max functions as well as a function on_error that determines how errors are handled. A common strategy would be to assert or throw and exception. The on_error is passed both the current value and the new value that is in error. constrained_value construct/copy/destructconstrained_value construct/copy/destruct1.constrained_value(value_type value);2.constrained_value& operator=(value_type v);constrained_value public member functionsconstrained_value public member functions1.operator value_type() const;Coerce into the representation type. constrained_value public static functionsconstrained_value public static functions1.value_type max BOOST_PREVENT_MACRO_SUBSTITUTION() ;Return the max allowed value (traits method). 2.value_type min BOOST_PREVENT_MACRO_SUBSTITUTION() ;Return the min allowed value (traits method). constrained_value private member functionsconstrained_value private member functions1.void assign(value_type value) ;Class template simple_exception_policyClass template simple_exception_policy -- Template to shortcut the constrained_value policy creation process. boost::CV::simple_exception_policytemplate<typename rep_type, rep_type min_value, rep_type max_value,
typename exception_type>
class simple_exception_policy {
public:
// types
typedef rep_type value_type;
// public static functions
rep_type min BOOST_PREVENT_MACRO_SUBSTITUTION() ;
rep_type max BOOST_PREVENT_MACRO_SUBSTITUTION() ;
void on_error(rep_type, rep_type, violation_enum) ;
};DescriptionDescriptionsimple_exception_policy public static functionssimple_exception_policy public static functions1.rep_type min BOOST_PREVENT_MACRO_SUBSTITUTION() ;2.rep_type max BOOST_PREVENT_MACRO_SUBSTITUTION() ;3.void on_error(rep_type , rep_type , violation_enum ) ;Header <boost/date_time/date.hpp>namespace boost {
namespace date_time {
template<typename T, typename calendar, typename duration_type_> class date;
}
}Class template dateClass template date -- Representation of timepoint at the one day level resolution. boost::date_time::datetemplate<typename T, typename calendar, typename duration_type_>
class date {
public:
// types
typedef T date_type;
typedef calendar calendar_type;
typedef calendar::date_traits_type traits_type;
typedef duration_type_ duration_type;
typedef calendar::year_type year_type;
typedef calendar::month_type month_type;
typedef calendar::day_type day_type;
typedef calendar::ymd_type ymd_type;
typedef calendar::date_rep_type date_rep_type;
typedef calendar::date_int_type date_int_type;
typedef calendar::day_of_week_type day_of_week_type;
// construct/copy/destruct
date(year_type, month_type, day_type);
date(const ymd_type &);
date(date_int_type);
date(date_rep_type);
// public member functions
year_type year() const;
month_type month() const;
day_type day() const;
day_of_week_type day_of_week() const;
ymd_type year_month_day() const;
bool operator<(const date_type &) const;
bool operator==(const date_type &) const;
bool is_special() const;
bool is_not_a_date() const;
bool is_infinity() const;
bool is_pos_infinity() const;
bool is_neg_infinity() const;
special_values as_special() const;
duration_type operator-(const date_type &) const;
date_type operator-(const duration_type &) const;
date_type operator-=(const duration_type &) ;
date_rep_type day_count() const;
date_type operator+(const duration_type &) const;
date_type operator+=(const duration_type &) ;
// protected member functions
};DescriptionDescriptionThe date template represents an interface shell for a date class that is based on a year-month-day system such as the gregorian or iso systems. It provides basic operations to enable calculation and comparisons.TheoryThis date representation fundamentally departs from the C tm struct approach. The goal for this type is to provide efficient date operations (add, subtract) and storage (minimize space to represent) in a concrete class. Thus, the date uses a count internally to represent a particular date. The calendar parameter defines the policies for converting the the year-month-day and internal counted form here. Applications that need to perform heavy formatting of the same date repeatedly will perform better by using the year-month-day representation.Internally the date uses a day number to represent the date. This is a monotonic time representation. This representation allows for fast comparison as well as simplifying the creation of writing numeric operations. Essentially, the internal day number is like adjusted julian day. The adjustment is determined by the Epoch date which is represented as day 1 of the calendar. Day 0 is reserved for negative infinity so that any actual date is automatically greater than negative infinity. When a date is constructed from a date or formatted for output, the appropriate conversions are applied to create the year, month, day representations. date construct/copy/destructdate construct/copy/destruct1.date(year_type y, month_type m, day_type d);2.date(const ymd_type & ymd);3.date(date_int_type days);This is a private constructor which allows for the creation of new dates. It is not exposed to users since that would require class users to understand the inner workings of the date class. 4.date(date_rep_type days);date public member functionsdate public member functions1.year_type year() const;2.month_type month() const;3.day_type day() const;4.day_of_week_type day_of_week() const;5.ymd_type year_month_day() const;6.bool operator<(const date_type & rhs) const;7.bool operator==(const date_type & rhs) const;8.bool is_special() const;check to see if date is a special value 9.bool is_not_a_date() const;check to see if date is not a value 10.bool is_infinity() const;check to see if date is one of the infinity values 11.bool is_pos_infinity() const;check to see if date is greater than all possible dates 12.bool is_neg_infinity() const;check to see if date is greater than all possible dates 13.special_values as_special() const;return as a special value or a not_special if a normal date 14.duration_type operator-(const date_type & d) const;15.date_type operator-(const duration_type & dd) const;16.date_type operator-=(const duration_type & dd) ;17.date_rep_type day_count() const;18.date_type operator+(const duration_type & dd) const;19.date_type operator+=(const duration_type & dd) ;date protected member functionsdate protected member functionsHeader <boost/date_time/date_clock_device.hpp>namespace boost {
namespace date_time {
template<typename date_type> class day_clock;
}
}Class template day_clockClass template day_clock -- A clock providing day level services based on C time_t capabilities. boost::date_time::day_clocktemplate<typename date_type>
class day_clock {
public:
// types
typedef date_type::ymd_type ymd_type;
// public static functions
date_type local_day() ;
date_type::ymd_type local_day_ymd() ;
date_type::ymd_type universal_day_ymd() ;
date_type universal_day() ;
// private static functions
::std::tm * get_local_time() ;
::std::tm * get_universal_time() ;
};DescriptionDescriptionThis clock uses Posix interfaces as its implementation and hence uses the timezone settings of the operating system. Incorrect user settings will result in incorrect results for the calls to local_day. day_clock public static functionsday_clock public static functions1.date_type local_day() ;Get the local day as a date type. 2.date_type::ymd_type local_day_ymd() ;Get the local day as a ymd_type. 3.date_type::ymd_type universal_day_ymd() ;Get the current day in universal date as a ymd_type. 4.date_type universal_day() ;Get the UTC day as a date type. day_clock private static functionsday_clock private static functions1.::std::tm * get_local_time() ;2.::std::tm * get_universal_time() ;Header <boost/date_time/date_defs.hpp>namespace boost {
namespace date_time {
// An enumeration of weekday names.
enum weekdays { Sunday, Monday, Tuesday, Wednesday, Thursday, Friday,
Saturday };
// Simple enum to allow for nice programming with Jan, Feb, etc.
enum months_of_year { Jan = 1, Feb, Mar, Apr, May, Jun, Jul, Aug, Sep, Oct,
Nov, Dec, NotAMonth, NumMonths };
}
}Header <boost/date_time/date_duration.hpp>namespace boost {
namespace date_time {
template<typename duration_rep_traits> class date_duration;
struct duration_traits_long;
struct duration_traits_adapted;
}
}Class template date_durationClass template date_duration -- Duration type with date level resolution. boost::date_time::date_durationtemplate<typename duration_rep_traits>
class date_duration {
public:
// types
typedef duration_rep_traits::int_type duration_rep_type;
typedef duration_rep_traits::impl_type duration_rep;
// construct/copy/destruct
date_duration(duration_rep);
date_duration(special_values);
date_duration(const date_duration< duration_rep_traits > &);
// public member functions
duration_rep get_rep() const;
bool is_special() const;
duration_rep_type days() const;
bool operator==(const date_duration &) const;
bool operator<(const date_duration &) const;
date_duration operator-=(const date_duration &) ;
date_duration operator+=(const date_duration &) ;
date_duration operator-() const;
date_duration< duration_rep_traits > operator/=(int) ;
date_duration< duration_rep_traits > operator/(int) ;
bool is_negative() const;
// public static functions
date_duration unit() ;
};DescriptionDescriptiondate_duration construct/copy/destructdate_duration construct/copy/destruct1.date_duration(duration_rep day_count);Construct from a day count. 2.date_duration(special_values sv);construct from special_values - only works when instantiated with duration_traits_adapted 3.date_duration(const date_duration< duration_rep_traits > & other);Construct from another date_duration (Copy Constructor). date_duration public member functionsdate_duration public member functions1.duration_rep get_rep() const;returns days_ as it's instantiated type - used for streaming 2.bool is_special() const;3.duration_rep_type days() const;returns days as value, not object. 4.bool operator==(const date_duration & rhs) const;Equality. 5.bool operator<(const date_duration & rhs) const;Less. 6.date_duration operator-=(const date_duration & rhs) ;Subtract another duration -- result is signed. 7.date_duration operator+=(const date_duration & rhs) ;Add a duration -- result is signed. 8.date_duration operator-() const;unary- Allows for dd = -date_duration(2); -> dd == -2 9.date_duration< duration_rep_traits > operator/=(int divisor) ;Division operations on a duration with an integer. 10.date_duration< duration_rep_traits > operator/(int divisor) ;11.bool is_negative() const;return sign information date_duration public static functionsdate_duration public static functions1.date_duration unit() ;Returns the smallest duration -- used by to calculate 'end'. Struct duration_traits_longStruct duration_traits_long -- boost::date_time::duration_traits_long
struct duration_traits_long {
// types
typedef long int_type;
typedef long impl_type;
// public static functions
int_type as_number(impl_type) ;
};DescriptionDescriptionStruct for instantiating date_duration with NO special values functionality. Allows for transparent implementation of either date_duration<long> or date_duration<int_adapter<long> > duration_traits_long public static functionsduration_traits_long public static functions1.int_type as_number(impl_type i) ;Struct duration_traits_adaptedStruct duration_traits_adapted -- boost::date_time::duration_traits_adapted
struct duration_traits_adapted {
// types
typedef long int_type;
typedef boost::date_time::int_adapter< long > impl_type;
// public static functions
int_type as_number(impl_type) ;
};DescriptionDescriptionStruct for instantiating date_duration WITH special values functionality. Allows for transparent implementation of either date_duration<long> or date_duration<int_adapter<long> > duration_traits_adapted public static functionsduration_traits_adapted public static functions1.int_type as_number(impl_type i) ;Header <boost/date_time/date_duration_types.hpp>namespace boost {
namespace date_time {
template<typename duration_config> class weeks_duration;
template<typename base_config> class months_duration;
template<typename base_config> class years_duration;
}
}Class template weeks_durationClass template weeks_duration -- Additional duration type that represents a number of n*7 days. boost::date_time::weeks_durationtemplate<typename duration_config>
class weeks_duration
: : public boost::date_time::date_duration< duration_config >
{
public:
// construct/copy/destruct
weeks_duration(typename duration_config::impl_type);
weeks_duration(special_values);
// public member functions
};DescriptionDescriptionweeks_duration construct/copy/destructweeks_duration construct/copy/destruct1.weeks_duration(typename duration_config::impl_type w);2.weeks_duration(special_values sv);weeks_duration public member functionsweeks_duration public member functionsClass template months_durationClass template months_duration -- additional duration type that represents a logical month boost::date_time::months_durationtemplate<typename base_config>
class months_duration {
public:
// construct/copy/destruct
months_duration(int_rep);
months_duration(special_values);
// public member functions
int_rep number_of_months() const;
duration_type get_neg_offset(const date_type &) const;
duration_type get_offset(const date_type &) const;
bool operator==(const months_type &) const;
bool operator!=(const months_type &) const;
months_type operator+(const months_type &) const;
months_type & operator+=(const months_type &) ;
months_type operator-(const months_type &) const;
months_type & operator-=(const months_type &) ;
months_type operator *(const int_type) const;
months_type & operator *=(const int_type) ;
months_type operator/(const int_type) const;
months_type & operator/=(const int_type) ;
months_type operator+(const years_type &) const;
months_type & operator+=(const years_type &) ;
months_type operator-(const years_type &) const;
months_type & operator-=(const years_type &) ;
};DescriptionDescriptionA logical month enables things like: "date(2002,Mar,2) + months(2) -> 2002-May2". If the date is a last day-of-the-month, the result will also be a last-day-of-the-month. months_duration construct/copy/destructmonths_duration construct/copy/destruct1.months_duration(int_rep num);2.months_duration(special_values sv);months_duration public member functionsmonths_duration public member functions1.int_rep number_of_months() const;2.duration_type get_neg_offset(const date_type & d) const;returns a negative duration 3.duration_type get_offset(const date_type & d) const;4.bool operator==(const months_type & rhs) const;5.bool operator!=(const months_type & rhs) const;6.months_type operator+(const months_type & rhs) const;7.months_type & operator+=(const months_type & rhs) ;8.months_type operator-(const months_type & rhs) const;9.months_type & operator-=(const months_type & rhs) ;10.months_type operator *(const int_type rhs) const;11.months_type & operator *=(const int_type rhs) ;12.months_type operator/(const int_type rhs) const;13.months_type & operator/=(const int_type rhs) ;14.months_type operator+(const years_type & y) const;15.months_type & operator+=(const years_type & y) ;16.months_type operator-(const years_type & y) const;17.months_type & operator-=(const years_type & y) ;Class template years_durationClass template years_duration -- additional duration type that represents a logical year boost::date_time::years_durationtemplate<typename base_config>
class years_duration {
public:
// construct/copy/destruct
years_duration(int_rep);
years_duration(special_values);
// public member functions
int_rep number_of_years() const;
duration_type get_neg_offset(const date_type &) const;
duration_type get_offset(const date_type &) const;
bool operator==(const years_type &) const;
bool operator!=(const years_type &) const;
years_type operator+(const years_type &) const;
years_type & operator+=(const years_type &) ;
years_type operator-(const years_type &) const;
years_type & operator-=(const years_type &) ;
years_type operator *(const int_type) const;
years_type & operator *=(const int_type) ;
years_type operator/(const int_type) const;
years_type & operator/=(const int_type) ;
months_type operator+(const months_type &) const;
months_type operator-(const months_type &) const;
};DescriptionDescriptionA logical year enables things like: "date(2002,Mar,2) + years(2) -> 2004-Mar-2". If the date is a last day-of-the-month, the result will also be a last-day-of-the-month (ie date(2001-Feb-28) + years(3) -> 2004-Feb-29). years_duration construct/copy/destructyears_duration construct/copy/destruct1.years_duration(int_rep num);2.years_duration(special_values sv);years_duration public member functionsyears_duration public member functions1.int_rep number_of_years() const;2.duration_type get_neg_offset(const date_type & d) const;returns a negative duration 3.duration_type get_offset(const date_type & d) const;4.bool operator==(const years_type & rhs) const;5.bool operator!=(const years_type & rhs) const;6.years_type operator+(const years_type & rhs) const;7.years_type & operator+=(const years_type & rhs) ;8.years_type operator-(const years_type & rhs) const;9.years_type & operator-=(const years_type & rhs) ;10.years_type operator *(const int_type rhs) const;11.years_type & operator *=(const int_type rhs) ;12.years_type operator/(const int_type rhs) const;13.years_type & operator/=(const int_type rhs) ;14.months_type operator+(const months_type & m) const;15.months_type operator-(const months_type & m) const;Header <boost/date_time/date_format_simple.hpp>namespace boost {
namespace date_time {
template<typename charT> class simple_format;
template<> class simple_format<wchar_t>;
}
}Class template simple_formatClass template simple_format -- Class to provide simple basic formatting rules. boost::date_time::simple_formattemplate<typename charT>
class simple_format {
public:
// public static functions
const charT * not_a_date() ;
const charT * pos_infinity() ;
const charT * neg_infinity() ;
month_format_spec month_format() ;
ymd_order_spec date_order() ;
bool has_date_sep_chars() ;
charT year_sep_char() ;
charT month_sep_char() ;
charT day_sep_char() ;
charT hour_sep_char() ;
charT minute_sep_char() ;
charT second_sep_char() ;
};DescriptionDescriptionsimple_format public static functionssimple_format public static functions1.const charT * not_a_date() ;String used printed is date is invalid. 2.const charT * pos_infinity() ;String used to for positive infinity value. 3.const charT * neg_infinity() ;String used to for positive infinity value. 4.month_format_spec month_format() ;Describe month format. 5.ymd_order_spec date_order() ;6.bool has_date_sep_chars() ;This format uses '-' to separate date elements. 7.charT year_sep_char() ;Char to sep? 8.charT month_sep_char() ;char between year-month 9.charT day_sep_char() ;Char to separate month-day. 10.charT hour_sep_char() ;char between date-hours 11.charT minute_sep_char() ;char between hour and minute 12.charT second_sep_char() ;char for second SpecializationsSpecializations•Class simple_format<wchar_t>Class simple_format<wchar_t>Class simple_format<wchar_t> -- Specialization of formmating rules for wchar_t. boost::date_time::simple_format<wchar_t>
class simple_format<wchar_t> {
public:
// public static functions
const wchar_t * not_a_date() ;
const wchar_t * pos_infinity() ;
const wchar_t * neg_infinity() ;
month_format_spec month_format() ;
ymd_order_spec date_order() ;
bool has_date_sep_chars() ;
wchar_t year_sep_char() ;
wchar_t month_sep_char() ;
wchar_t day_sep_char() ;
wchar_t hour_sep_char() ;
wchar_t minute_sep_char() ;
wchar_t second_sep_char() ;
};DescriptionDescriptionsimple_format public static functionssimple_format public static functions1.const wchar_t * not_a_date() ;String used printed is date is invalid. 2.const wchar_t * pos_infinity() ;String used to for positive infinity value. 3.const wchar_t * neg_infinity() ;String used to for positive infinity value. 4.month_format_spec month_format() ;Describe month format. 5.ymd_order_spec date_order() ;6.bool has_date_sep_chars() ;This format uses '-' to separate date elements. 7.wchar_t year_sep_char() ;Char to sep? 8.wchar_t month_sep_char() ;char between year-month 9.wchar_t day_sep_char() ;Char to separate month-day. 10.wchar_t hour_sep_char() ;char between date-hours 11.wchar_t minute_sep_char() ;char between hour and minute 12.wchar_t second_sep_char() ;char for second Header <boost/date_time/date_formatting.hpp>namespace boost {
namespace date_time {
template<typename month_type, typename format_type, typename charT = char>
class month_formatter;
template<typename ymd_type, typename format_type, typename charT = char>
class ymd_formatter;
template<typename date_type, typename format_type, typename charT = char>
class date_formatter;
}
}Class template month_formatterClass template month_formatter -- Formats a month as as string into an ostream. boost::date_time::month_formattertemplate<typename month_type, typename format_type, typename charT = char>
class month_formatter {
public:
// public static functions
std::basic_ostream< charT > &
format_month(const month_type &, std::basic_ostream< charT > &) ;
std::ostream & format_month(const month_type &, std::ostream &) ;
};DescriptionDescriptionmonth_formatter public static functionsmonth_formatter public static functions1.std::basic_ostream< charT > &
format_month(const month_type & month, std::basic_ostream< charT > & os) ;Formats a month as as string into an ostream. This function demands that month_type provide functions for converting to short and long strings if that capability is used. 2.std::ostream & format_month(const month_type & month, std::ostream & os) ;Formats a month as as string into an ostream. This function demands that month_type provide functions for converting to short and long strings if that capability is used. Class template ymd_formatterClass template ymd_formatter -- Convert ymd to a standard string formatting policies. boost::date_time::ymd_formattertemplate<typename ymd_type, typename format_type, typename charT = char>
class ymd_formatter {
public:
// public static functions
std::basic_string< charT > ymd_to_string(ymd_type) ;
std::string ymd_to_string(ymd_type) ;
};DescriptionDescriptionymd_formatter public static functionsymd_formatter public static functions1.std::basic_string< charT > ymd_to_string(ymd_type ymd) ;Convert ymd to a standard string formatting policies. This is standard code for handling date formatting with year-month-day based date information. This function uses the format_type to control whether the string will contain separator characters, and if so what the character will be. In addtion, it can format the month as either an integer or a string as controled by the formatting policy 2.std::string ymd_to_string(ymd_type ymd) ;Convert ymd to a standard string formatting policies. This is standard code for handling date formatting with year-month-day based date information. This function uses the format_type to control whether the string will contain separator characters, and if so what the character will be. In addtion, it can format the month as either an integer or a string as controled by the formatting policy Class template date_formatterClass template date_formatter -- Convert a date to string using format policies. boost::date_time::date_formattertemplate<typename date_type, typename format_type, typename charT = char>
class date_formatter {
public:
// types
typedef std::basic_string< charT > string_type;
// public static functions
string_type date_to_string(date_type) ;
std::string date_to_string(date_type) ;
};DescriptionDescriptiondate_formatter public static functionsdate_formatter public static functions1.string_type date_to_string(date_type d) ;Convert to a date to standard string using format policies. 2.std::string date_to_string(date_type d) ;Convert to a date to standard string using format policies. Header <boost/date_time/date_formatting_limited.hpp>namespace boost {
namespace date_time {
}
}