summaryrefslogtreecommitdiff
path: root/src/times.h
Commit message (Collapse)AuthorAgeFilesLines
* Add new --align-intervals option.Ian20202024-08-061-5/+8
|
* Use #pragma onceAlexis Hildebrandt2023-04-101-4/+1
|
* Update copyright yearAlexis Hildebrandt2023-02-021-1/+1
| | | | [skip ci]
* Update copyright statement for 2022Alexis Hildebrandt2022-07-021-1/+1
|
* Change header guard names to use `INCLUDED_` prefixPhil Newton2022-04-061-3/+3
| | | | Fixes #2049
* [misc] Update year in copyright notice to 2017Alexis Hildebrandt2018-01-271-1/+1
| | | | [ci skip]
* [misc] Update year in copyright notice to 2017Alexis Hildebrandt2017-01-051-1/+1
| | | | [ci skip]
* [misc] Update year in copyright notice to 2016Alexis Hildebrandt2016-01-021-1/+1
| | | | [ci skip]
* Convert boost::optional objects to bool explicitly.Jonathan Wakely2015-07-271-5/+1
| | | | Fixes #417.
* Revert "boost::none_t no longer convertible from literal 0 in 1.58"John Wiegley2015-05-171-1/+5
| | | | This reverts commit 48aec0f093ff6494a3e4f7cd5166cb4a27c16814.
* boost::none_t no longer convertible from literal 0 in 1.58Johann Klähn2015-05-101-5/+1
| | | | Instead we use boost::none, which has been documented since boost 1.34.0.
* [ledger] Remove --cache optionAlexis Hildebrandt2015-02-181-86/+0
| | | | and all boost serialisation related code.
* Bump copyright notice to 2015Alexis Hildebrandt2014-12-271-1/+1
| | | | | | The following script makes it a no-brainer: % NEXT_YEAR=2015; ag -l 'Copyright.*Wiegley' \ | xargs sed -i '' -e "s/\(Copyright.*\)-20[0-9]\{2\}/\1-${NEXT_YEAR}/"
* #if guards for boost 1.56 compatibilityJoe Gallo2014-08-281-0/+4
|
* Revert "fix "no viable conversion from ... to 'bool'""John Wiegley2014-08-271-1/+1
| | | | This reverts commit df9ae3ab9b37fde803f26c6bc4eaadfd67fc1d07.
* fix "no viable conversion from ... to 'bool'"Joe Gallo2014-08-261-1/+1
|
* Bump copyright information to 2014Alexis Hildebrandt2014-02-021-1/+1
|
* fix ledger xml output, remove ledger json commandJohann Klähn2013-03-081-12/+4
| | | | | | | | | | | | As the format used by property trees to represent valid JSON and that for valid XML is too different and given that there are more requests for valid XML output I decided to pursue a quick fix and remove the json command in favor of a working xml command. See bug #782, #909, recent discussion on mailing list. JSON support is postponed until I or someone else finds time to work on this or the python bindings are more stable.
* Bump copyright information to 2013John Wiegley2013-02-181-1/+1
|
* Converted the Ledger build system to use CMakeJohn Wiegley2012-05-201-6/+6
|
* Switched to Boost.PropertyTree for XML generationJohn Wiegley2012-05-181-18/+12
|
* Always call TRACE_CTOR at the end of constructorsJohn Wiegley2012-03-201-2/+3
|
* Added #if's for building optimized with ClangJohn Wiegley2012-03-071-0/+4
|
* Corrected several compile and link problemsJohn Wiegley2012-03-061-0/+2
|
* Increased file copyrights to 2012John Wiegley2012-02-291-1/+1
|
* Rewrite the way interval reports are generatedJohn Wiegley2012-02-281-4/+8
|
* Fixed nasty problem related to interval reportingJohn Wiegley2012-02-281-0/+4
|
* Removed unneeded default casesJohn Wiegley2012-02-171-7/+0
|
* Cleanup whitespaceJohn Wiegley2011-08-181-2/+2
|
* The notions of "now" and "today" now use local timeJohn Wiegley2010-06-221-3/+3
|
* Revised how Ledger handles the "current year"John Wiegley2010-06-141-37/+31
| | | | | Now when the Y directive sets the current year for a region, it affects everything, as if the clock really were set back to that year.
* Untabified all source filesJohn Wiegley2010-06-111-49/+49
|
* Corrected a typename visibility issueJohn Wiegley2010-06-061-0/+2
|
* Updated copyrights to 2003-2010John Wiegley2010-03-051-1/+1
|
* Wasn't serializing date_range_t::end_inclusive memberJohn Wiegley2009-11-181-0/+1
|
* The new period parser is passing all testsJohn Wiegley2009-11-181-15/+3
|
* The new period parser is implemented, but untestedJohn Wiegley2009-11-181-272/+228
|
* Added a "range" member to date_interval_tJohn Wiegley2009-11-181-19/+26
| | | | | | This is used to define the beginning/ending ranges of the time period, before it becomes fixed (by calling stabilize()) and then sets the values of start and end.
* Added several new types for working with dates and rangesJohn Wiegley2009-11-171-0/+327
| | | | | | | | | | | | | | | | | | | | | | | | date_specifier_t :: This is like a plain date_t, except it knows what wasn't specified. For example, if 2008/06 is parsed, it becomes date_specifier_t which knows that no day was given. If you ask for the begin() date of the specifier, it will be 2008/06/01; the end() date (which is exclusive) will be 2008/07/01. date_range_t :: A date range is a range of two specifiers, either of which (but not both) may be omitted. This makes it possible to represent expressions like "from june to july", where no day or year is given. The exact dates will be inferred by using the current year, and fixing the range from YEAR/06/01 to YEAR/07/01. That is, the range goes from the begin() of one date specifier to the begin() of the other. date_specifier_or_range_t :: A variadic type that can be either a date_specifier_t or a date_range_t. It's just a wrapper to represent the fact that ranges can be implicit via specifiers (such as, "in june"), or explicit via ranges ("since 2008").
* Moved date_interval_t::duration_t to date_duration_tJohn Wiegley2009-11-171-79/+77
|
* Added a date_traits_t typeJohn Wiegley2009-11-171-0/+44
|
* Renamed date_interval_t::end to finishJohn Wiegley2009-11-171-3/+3
|
* Stylistic change: assert(0) -> assert(false)John Wiegley2009-11-131-2/+2
|
* XML reporting now works via the "xml" commandJohn Wiegley2009-11-091-6/+16
|
* Added basic foundation for XML reportingJohn Wiegley2009-11-091-0/+12
|
* Whitespace fixJohn Wiegley2009-11-041-2/+2
|
* Added serialization methods for most typeJohn Wiegley2009-10-301-0/+32
| | | | | This allows journal_t objects to be completed serialized to disk and deserialized.
* date_interval_t now uses a duration_t objectJohn Wiegley2009-10-301-4/+52
| | | | This is instead of using boost::variant.
* Added TRUE_CURRENT_TIME() macroJohn Wiegley2009-10-281-4/+4
| | | | Because CURRENT_TIME() can now be a past date if --now is used.
* Support a --now option, for testing purposesJohn Wiegley2009-10-271-3/+8
| | | | | | This sets Ledger's notion of the "current time" to the given date. This makes it possible to have stable output from budgeting and forecasting reports, for the sake of baseline tests.