summaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAgeFilesLines
* Extended proof/push to upload tarballs/gcovJohn Wiegley2010-06-152-8/+32
|
* v3.0.0-20100615John Wiegley2010-06-151-1/+1
|
* Corrected the 'report' rule in Makefile.amJohn Wiegley2010-06-151-3/+3
|
* Merge branch 'next'John Wiegley2010-06-1533-139/+242
|\
| * Changes for building with Visual Studio 2008John Wiegley2010-06-1518-28/+42
| |
| * Corrected list of options shown in the man pageJohn Wiegley2010-06-151-8/+39
| |
| * Removed unused --unsorted optionJohn Wiegley2010-06-156-13/+3
| |
| * Version information is now based on version.m4John Wiegley2010-06-155-63/+49
| |
| * Tests run in parallel with using acprep -jX makeJohn Wiegley2010-06-155-27/+109
|/ | | | | This is done using the multiprocessing library in Python 2.6. If that's unavailable, this feature does nothing.
* Merge branch 'next'John Wiegley2010-06-1464-511/+785
|\
| * Support period expressions "this/next/last week"John Wiegley2010-06-141-14/+28
| |
| * Allow period exprs "from today", "until tomorrow"John Wiegley2010-06-141-0/+10
| |
| * Support period expressions like "last 4 weeks"John Wiegley2010-06-141-12/+37
| |
| * Fix to allow time periods like "every 14 days"John Wiegley2010-06-141-1/+1
| |
| * Improved algorithm for abbreviating account namesJohn Wiegley2010-06-1434-231/+354
| |
| * Made >>>2 and === optional in regression testsJohn Wiegley2010-06-141-5/+6
| |
| * Added `ledger-update-test' to ldg-texi.elJohn Wiegley2010-06-141-0/+20
| |
| * Added initial implementation of lot_*() functionsJohn Wiegley2010-06-142-1/+37
| |
| * Don't elide quotes for all-digit commoditiesJohn Wiegley2010-06-141-3/+7
| |
| * Revised how Ledger handles the "current year"John Wiegley2010-06-1416-152/+126
| | | | | | | | | | 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.
| * Moved temps.cc into libdataJohn Wiegley2010-06-141-2/+2
| |
| * Removed some unneeded codeJohn Wiegley2010-06-141-18/+7
| |
| * Corrected bug with forecasting date bounded xactsJohn Wiegley2010-06-133-48/+57
| |
| * Restored min() and max() virtual functionsJohn Wiegley2010-06-132-0/+20
| |
| * When parsing date expressions, assume current yearJohn Wiegley2010-06-131-1/+1
| |
| * Added a missing break statementJohn Wiegley2010-06-131-0/+1
| | | | | | | | This broke the meaning of -p "this month".
| * Removed a needless Python 2.6ism from acprepJohn Wiegley2010-06-131-1/+4
| |
| * Fixed several misplaced parenthesesJohn Wiegley2010-06-132-6/+6
| |
| * Report error context in expressions more preciselyJohn Wiegley2010-06-136-17/+27
| |
| * Created tools/speed-test.sh for speed testingJohn Wiegley2010-06-131-0/+18
| |
| * Fix python demo: EUROPEAN was changed to DECIMAL_COMMAPriit Laes2010-06-131-2/+2
| | | | | | | | Signed-off-by: Priit Laes <plaes@plaes.org>
| * Added --prefix option to acprepPriit Laes2010-06-131-1/+18
|/ | | | Signed-off-by: Priit Laes <plaes@plaes.org>
* Merge branch 'next'John Wiegley2010-06-1336-970/+1090
|\
| * Removed an invalid called to VERIFY()John Wiegley2010-06-131-1/+0
| |
| * Fixed documentation bug in acprepJohn Wiegley2010-06-131-1/+1
| |
| * The --cache option is now officially deprecatedJohn Wiegley2010-06-131-30/+31
| |
| * Fixes to scope.h for the sake of Boost.SerializationJohn Wiegley2010-06-131-2/+21
| |
| * Removed unneeded debug codeJohn Wiegley2010-06-131-5/+0
| |
| * Completely reworked argument passing in expressionsJohn Wiegley2010-06-1322-752/+533
| |
| * In value_t::_dup, test if storage is uninitializedJohn Wiegley2010-06-131-1/+1
| |
| * For value_t, use boost::any to refer to objectsJohn Wiegley2010-06-133-52/+75
| |
| * Moved value_t::label() to value.ccJohn Wiegley2010-06-132-33/+40
| |
| * Improved support for value_t::in_place* functionsJohn Wiegley2010-06-131-36/+26
| |
| * Moved join_args function to precmd.ccJohn Wiegley2010-06-131-0/+16
| |
| * Changed display order of format exceptionsJohn Wiegley2010-06-131-0/+5
| |
| * Further tweaks to tools/pushJohn Wiegley2010-06-131-2/+3
| |
| * If a type context exists, confirm the result matchesJohn Wiegley2010-06-132-5/+19
| |
| * Expression evaluations now have a "type context"John Wiegley2010-06-134-38/+54
| | | | | | | | | | | | | | | | | | Thus, an expression can know if the context in which it's being evaluated requires a string, and if so, determine it's output accordingly. For example: account ; returns the full name of the posting's account account.total ; here the context is SCOPE, so account is an obj
| * Added a new scope_value() inline helper functionJohn Wiegley2010-06-135-12/+12
| |
| * Added support for assert, check and expr directivesJohn Wiegley2010-06-133-18/+161
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | These can occur in many places: ; Within an automated transaction, the assert is evaluated every time ; a posting is matched, with the expression context set to the ; matching posting. = /Food/ assert account("Expenses:Food").total >= $100 2010-06-12 Sample Expenses:Food $100 Assets:Checking ; At file scope, the expression is evaluated with "global" scope. assert account("Expenses:Food").total == $100 ; At the top of a transction, the assertion's scope is the ; transaction. After a posting, the scope is that posting. Note ; however that account totals are only adjusted after successful ; parsing of a transaction, which means that all the assertions below ; are true, even though it appears as though the middle posting should ; affect the total immediately (which is not the case). 2010-06-12 Sample 2 assert account("Expenses:Food").total == $100 Expenses:Food $50 assert account("Expenses:Food").total == $100 Assets:Checking assert account("Expenses:Food").total == $100