Scheduled transactions question

[Josh Sled]

Guillaume Lessard <glessard at tffenterprises.com> writes:
> I've been using gnucash for a long time, and I just recently concluded  that
> there might just be a bug in the 2.x version of scheduled  transactions:
>
> Values for the various splits are stored as strings.

Yes, there is.  http://bugzilla.gnome.org/show_bug.cgi?id=170729

> I'm holding off on the bug report for now, because I seem to remember  that
> it didn't work that way in the old scheduled transactions module  (from
> 1.8.x); is there a good reason to store these numbers as strings?

This was true in 1.8.x as well.

The credit/debit cells in template transactions are formulae, and while
they are parsed and evaluated at runtime, they are stored as raw string
literals.  There is no good reason except developer laziness/simplicity;
it is unfortunate that numeric portions are not stored in a
locale-independent manner, at least.

-- 
...jsled
http://asynchronous.org/ - a=jsled; b=asynchronous.org; echo ${a}@${b}
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 197 bytes
Desc: not available
URL: <http://lists.gnucash.org/pipermail/gnucash-user/attachments/20090818/1acddf58/attachment.bin>