summaryrefslogtreecommitdiff
path: root/src/times.h
Commit message (Collapse)AuthorAgeFilesLines
* 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.
* Rewrote the way date and time I/O is managedJohn Wiegley2009-10-251-26/+15
|
* Removed reliance on strptime/strftimeJohn Wiegley2009-10-111-24/+21
| | | | | | | | The code now uses Boost's input and output facets for times and dates. This ensures completely consistency regarding timezones and times, and fixes the regression test that was broken while I was away coding in London (where it was GMT-0 and I didn't notice the difference between local and GMT).
* Added some missing casts, upgraded to Boost 1.40John Wiegley2009-10-091-1/+1
|
* Rewrote the date interval parser/stepperJohn Wiegley2009-03-231-3/+7
| | | | | The new implementation uses boost::gregorian::date_duration objects, rather than manually stepping.
* The new code is working now.John Wiegley2009-03-161-3/+7
|
* Added feature to "align" the interval's start dateJohn Wiegley2009-03-151-2/+6
|
* First iteration of the new date_interval_t rewriteJohn Wiegley2009-03-151-71/+61
|
* Started breaking up interval_t into range_tJohn Wiegley2009-03-151-14/+43
|
* Reduced the #include dependency tree to a minimumJohn Wiegley2009-03-041-0/+2
|
* Greatly improved the way "weeks" are iteratedJohn Wiegley2009-02-211-6/+15
|
* Fixed the way interval_t objects are initializedJohn Wiegley2009-02-141-2/+2
|
* Removed interval_t::advanced, which was unusedJohn Wiegley2009-02-141-6/+3
|
* Fixed the use of --effective and --date-format (-y).John Wiegley2009-02-091-9/+15
|
* Largely removed all of Ledger's use of global variables, for the REPL's sake.John Wiegley2009-02-041-24/+22
|
* Added documentation stubs for all include files and classes.John Wiegley2009-01-311-1/+5
|
* Update Doxygen documentation. Still much more work to be done.John Wiegley2009-01-291-0/+13
|
* Changed order of some functions, to guard against self-referencing.John Wiegley2009-01-241-2/+4
|
* Increased copyright range to include 2009.John Wiegley2009-01-201-1/+1
|
* Restored --format, --date-format (-y), and --input-date-format options.John Wiegley2008-09-141-2/+3
|
* Changed interval_t::start to interval_t::set_start, to be more clear about howJohn Wiegley2008-08-141-2/+3
| | | | it differs from interval_t::first.
* Changed the default output date format in register reports from 2008-08-13 toJohn Wiegley2008-08-131-1/+1
| | | | | | 08-Aug-13. This allows for the account name to be one character wider, while the century was never significant in people's minds, whereas the change in months between two transactions sometimes is.
* Moved around most of the files so that source code is in src/, documentationJohn Wiegley2008-08-051-0/+154
is in doc/, etc.
generated by cgit v1.2.3 (git 2.39.1) at 2025-01-07 22:57:44 +0000