summaryrefslogtreecommitdiff
path: root/src
Commit message (Collapse)AuthorAgeFilesLines
...
* The new period parser is implemented, but untestedJohn Wiegley2009-11-183-629/+883
|
* Added a "range" member to date_interval_tJohn Wiegley2009-11-182-30/+34
| | | | | | 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-172-0/+615
| | | | | | | | | | | | | | | | | | | | | | | | 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-172-108/+106
|
* Added a date_traits_t typeJohn Wiegley2009-11-172-26/+68
|
* Renamed date_interval_t::end to finishJohn Wiegley2009-11-176-52/+52
|
* Some reformatting in query.hJohn Wiegley2009-11-171-35/+37
|
* Added ledger::string(Iter, Iter) constructorJohn Wiegley2009-11-171-0/+5
|
* Fixed several time and date duration type usesJohn Wiegley2009-11-172-9/+16
|
* Made the account and tag directives more rationalJohn Wiegley2009-11-151-69/+81
| | | | | Now you must specify "account / end account", and "tag / end tag". For backwards compatability, plain "end" is the same as "end account".
* Corrected parsing of the 'expr' report query termJohn Wiegley2009-11-152-10/+14
|
* Made the transaction date parser a bit more strictJohn Wiegley2009-11-151-10/+13
|
* Made the amount_t::bigint_t refcount holder 32-bitsJohn Wiegley2009-11-141-6/+2
| | | | It was overflowing on a full register report of just 3M of data.
* Changed a use of balance_error to amount_errorJohn Wiegley2009-11-141-1/+1
|
* Added another catch handler for Python exceptionsJohn Wiegley2009-11-141-0/+4
|
* Fixed an internal reference issue with PythonJohn Wiegley2009-11-142-13/+29
|
* Removed post_t::xdata_t::ptr, which is not usedJohn Wiegley2009-11-141-4/+1
|
* Memoize results from the fast predicate matcherJohn Wiegley2009-11-142-1/+18
| | | | | This gains another 15% for the parser, again with a very simple change that has no impact if the fast predicate matcher fails to work.
* Spot optimization for simple automated xact exprsJohn Wiegley2009-11-142-5/+70
| | | | | | This reduces parsing time in the optimized build by 25%, and was a safe, easy patch. If the "quick predicate evaluator" fails, we disable it from that point on go back to what the standard code does.
* Removed the virtual marker on several filter methodsJohn Wiegley2009-11-141-4/+4
|
* Added historical support for single-letter valexprsJohn Wiegley2009-11-144-3/+90
|
* Optimization in the formatting of string valuesJohn Wiegley2009-11-142-3/+9
|
* Break up multiple commodities in equity reportJohn Wiegley2009-11-142-11/+18
|
* Don't bold the payee for virtual or temporary xactsJohn Wiegley2009-11-131-1/+1
|
* Stylistic change: assert(0) -> assert(false)John Wiegley2009-11-136-11/+11
|
* Fixed some debug outputJohn Wiegley2009-11-131-0/+5
|
* --data shouldn't modify the underlying itemJohn Wiegley2009-11-122-7/+1
|
* Move a typedef in utils.hJohn Wiegley2009-11-121-4/+4
|
* Added a Journal.collect method to PythonJohn Wiegley2009-11-121-0/+106
| | | | | | | | | | | | | | | | | | | | This lets you run standard report queries against a Ledger journal and get back a collection of postings, for example: import ledger journal = ledger.Journal("sample.dat") posts = journal.collect("-M assets") for post in posts: print post.account However, this code is not really working yet for a large variety of reasons, having to do with object life-time, shallow copying, and lack of reference counting where it should be. For instance, calling ledger.Journal().collect() fails because the temporary journal object is destroyed and the collection now has a host of bad pointers. Using "for post in journal.collect()" fails too with other bad pointers. And the whole lot of it crashes on exit at the moment.
* Removed unnecessary codeJohn Wiegley2009-11-121-1/+1
|
* Set call policies for accessing post.xdata.accountJohn Wiegley2009-11-121-2/+4
|
* Added a collect_posts handlerJohn Wiegley2009-11-121-0/+29
|
* Reordered the export_ calls in pyinterp.ccJohn Wiegley2009-11-121-6/+6
|
* Reorganized a bit of the reporting codeJohn Wiegley2009-11-122-48/+55
|
* Added has_xdata() methods for journal_t and xact_tJohn Wiegley2009-11-128-2/+45
|
* Made ~post_t virtualJohn Wiegley2009-11-121-1/+1
|
* session_t now holds a std::auto_prt<journal_t>John Wiegley2009-11-124-19/+19
|
* Moved report normalization into report.ccJohn Wiegley2009-11-124-174/+174
|
* Removed unused codeJohn Wiegley2009-11-121-2/+0
|
* Renamed the pricesdb command to pricedbJohn Wiegley2009-11-122-7/+7
|
* Added new value expressions for value conversionJohn Wiegley2009-11-112-0/+90
| | | | | | | | | | | | | | They are: to_boolean to_int to_datetime to_date to_amount to_balance to_string to_mask to_sequence
* Transactions now verified after applying auto xactsJohn Wiegley2009-11-112-1/+59
| | | | | This way you cannot violate the balancing rules, not even by adding a stray posting via an automated transaction.
* Added --date, similar to --account and --payeeJohn Wiegley2009-11-117-5/+31
| | | | | | | This lets you do things like store a date as the value of a tag, then run: ledger --date='has_tag("Foo") ? to_date(tag("Foo")) : date' reg
* Did away with the "finalizer" abstractionJohn Wiegley2009-11-117-245/+11
| | | | | This was from an earlier time, when it was intended to be used by Python. But it's not needed anymore.
* Use ledger::string only if VERIFY_ON or BOOST_PYTHONJohn Wiegley2009-11-112-0/+12
|
* Restore the Doxygen documentation buildJohn Wiegley2009-11-111-5/+5
|
* Value.to_sequence returns a valid Python sequenceJohn Wiegley2009-11-112-0/+5
|
* Added some missing calls to add_postJohn Wiegley2009-11-112-0/+3
|
* Added floor() value expression functionJohn Wiegley2009-11-112-0/+9
|
* Automated postings defer amount expression calculationJohn Wiegley2009-11-118-67/+93
| | | | | | | | | | | | | | | | | This allows for value expressions to be used which reference the incoming posting, for example: = Income:Clients: (Liabilities:Taxes:VAT1) (floor(amount) * 1) (Liabilities:Taxes:VAT2) 0.19 2009/07/27 * Invoice Assets:Bank:Checking $1,190.45 Income:Clients:ACME_Inc The automated posting for VAT1 will use the floored amount multiplied by a factor, while the posting for VAT2 multiples the whole amount as before.
generated by cgit v1.2.3 (git 2.39.1) at 2025-01-08 20:12:52 +0000