It's been rumoured that Rob Browning said:
>
> Jeremy Collins <[EMAIL PROTECTED]> writes:
>
> > I do however think we should settle on just using guile, and drop perl.
> > I am assuming that swig is still around for perl sake. So lets drop
> > perl, and swig already! ;) I am sure the reports code can be redone to
> > use guile somehow.
>
> That's fine with me. I'll even translate the reports code (or at
> least help whoever's doing it) if we decide to do go this way. This
> would remove at least one of the bigger dependencies.
>
> Linas, your thoughts?
Hmm,
The reports code should be done in guile for the technical reason
that I can't seem to/don't know how to invoke perl in the same address
space where the data exists. This requires data to be piped to the perl
process, which is slow.
------
But that's only part of the point. There are also some 'stand-alone'
perl scripts that scan a gnucash data file, find anything that's a stock
finds the right website, grabs the current price, and puts that price into
the data file. There are multiple (unrelated) issues here:
1) the code is just big enough that redoing in scheme seems like a waste
of time ...
2) these 'stand-alone' scripts are not currently invokable from a gnucash
menu entry; they must be run from the command line. ...
3) these scripts typically would get scheduled from a cron job.
Great answer for unix gurus, but a problem for newbies.
--linas
----- %< -------------------------------------------- >% ------
The GnuCash / X-Accountant Mailing List
To unsubscribe, send mail to [EMAIL PROTECTED] and
put "unsubscribe gnucash-devel [EMAIL PROTECTED]" in the body