Richard Wackerbarth wrote:
> One advantage that gnucash has it that it is multi-currency.
> That makes it easier to have one account in "dollars" in
> NewYork; another in "Francs" in Paris; and a third in
> "soybeans" in Raleigh.
>
> I don't have a different ENGINE for each of those. I just
> have different ACCOUNTS.
>
> Back to Matt's rabbit example, I need to track the number of
> rabbits that die.
>
> It IS important when I apply for disaster relief. (Well, they
> were really pigs, not rabbits. But the same principles apply.)
I was not trying to imply that accounting for your rabbits was
unnecessary. In fact, if you care about your rabbit investment, it is
absolutely necessary.
I am only questioning whether the "rabbit accounting" properly belongs
in the scope of the core engine. What I am really getting at here is
that the core engine should be modularly extensible in order to
accommodate all accounting situations, including ones that we have not
even thought of yet.
The core engine logs events in terms of a "currency", correct. Beyond
that, if you want to make any statements about the activity in terms
other than that currency, you are out of luck unless you encode the
extra translation information into the core engine, where it is not
strictly necessary.
Just as an aside, I deliberately chose rabbits in my example as an
analogy to stocks and splits. In this case, if the currency is "rabbits"
(ie, stock shares), there is a problem when they breed (split). You have
more "currency", but in order to represent this you have to keep
detailed breeding transactions with no exchange between accounts. This
is needless effort. It seems easier to simply log transactions in terms
of cash units for core accounting, and track the breeding behavior in a
specialized log/report.
--
Matt
--
Gnucash Developer's List
To unsubscribe send empty email to: [EMAIL PROTECTED]
