fork-ledger.git -

	Commit message (Collapse)	Author	Age	Files	Lines
*	Moved around most of the files so that source code is in src/, documentation	John Wiegley	2008-08-05	1	-1130/+0
\| \| \| \|	is in doc/, etc.
*	Regular expressions are working again, such that very basic register reports	John Wiegley	2008-08-03	1	-42/+0
\| \| \| \|	are now possible.
*	Moved xact_xdata_t into xact_t itself, as a set of "extended data" that might	John Wiegley	2008-08-02	1	-28/+0
\| \| \| \| \| \| \| \|	be gathered during reporting. Removed the references to accounts and such from the mask logic, which means that the value expression "acount =~ /foo/" is needed in place of just "/foo/".
*	Changed the way that bare masks are parsed. There is still some coupling	John Wiegley	2008-08-02	1	-2/+30
\| \| \| \|	here, albeit just through flag values. It needs to be changed, though.
*	Formatting now relies exclusively on value expressions.	John Wiegley	2008-08-02	1	-8/+25
\| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \|	What this means is that the utility code, basic math, value expressions, string formatting and option handling are now entirely decoupled from the rest of the code. This decoupling not only greatly simplifies the more basic parts of Ledger, but makes it much easier to test and verify its completeness. For example, when the formatting code %X is seen by the format parser, it turns into a call to the expression function fmt_X, which must be defined when the format string is first compiled against an object. If that object is a transaction, the transaction's scope will be the first to have a chance at providing a definition. If an account is being reported, it will. If neither does, the next scope in sequence -- soon to be the current report -- will, and then the session object that "owns" the current Ledger session. In 2.6, the formatting code new everything about transaction and accounts, and relied on flags to communicate special details between them. Now the transaction will offer the details for its own reporting, while the formatter worries only about strings and how to output them.
*	Journal data structures now use date_t instead of datetime_t.	John Wiegley	2008-08-01	1	-4/+4
\| \| \| \| \| \| \| \|	This means transactions can only have day-level granularity -- which has always been the case from an data file point of view. The advantage to this restriction is that reports will now be immune from daylight savings related bugs, where a transaction falls to the wrong side of a --monthly report, for example.
*	Improved the output from some debugging commands.	John Wiegley	2008-08-01	1	-3/+6
\| \| \| \| \| \| \| \| \|	There are now three commands one can use to interact with value expressions directly: ledger parse EXPR # shows the parse tree resulting from EXPR ledger compile EXPR # shows what the compiled tree looks like ledger eval EXPR # print the resulting value, useful in scripts
*	Change many uses of for+iterator to use Boost.Foreach.	John Wiegley	2008-07-31	1	-4/+2
\|
*	Revised the way that exceptions are thrown around. Instead of context being a	John Wiegley	2008-07-31	1	-28/+29
\| \| \| \| \| \| \|	complicated string of pointers, it's now just a global block of text that gets appended to as the error is being thrown up, and can be displayed at the catch point if desired. There are almost no cases where a thrown exception will not result in an error message being displayed to the user.
*	Enabled a huge number of warning flags for g++ in acprep, and fixed them all	John Wiegley	2008-07-30	1	-3/+3
\| \| \| \| \| \|	except for several unused parameter warnings (because there is so much code still #if 0'd out), and one implicit conversion from long long to long which still has to be dealt with.
*	The next value expression scheme is working, but the individual accessor	John Wiegley	2008-07-29	1	-5/+7
\| \| \| \|	functions for each of the journal objects has yet to be ported.
*	Moved around and renamed a very large amount of code in order to rationalize	John Wiegley	2008-07-29	1	-34/+34
\| \| \| \|	the way that value expressions extract information from journal objects.
*	Move the value expression code into libamounts, since it really belongs with	John Wiegley	2008-07-29	1	-2/+2
\| \| \| \|	value_t, rather than the rest of Ledger proper.
*	Value expression architecture is now rewritten, but the functionality of the	John Wiegley	2008-07-29	1	-0/+1151
	old system (for example, the meaning of 'a') has yet to be restored. In the new scheme, this will be done by definition a function outside of the value expression logic, rather than the tight coupling between journal innards and value expressions that occurred in 2.x.