Python report-writing mechanism?

[Josh Sled]

On Tue, 2007-03-06 at 19:19 -0600, Jeff Carneal wrote:
> Would it be fair to say that rewriting any or all of these in C is a  
> medium to long term goal of the project?  Because I have given some  

Yes.

My hope after finishing SX work for 2.2 release is to rework the core
reporting code to allow another option besides scheme, then to introduce
another language as the "sanctioned" reporting language, then to migrate
the reports themselves.

Given all manner of discussion we've had over the last few years in IRC,
it's not quite clear what that other language will be.  I'm pretty sure
it won't be C entirely ... there's definitely a space for a higher-level
language in the reporting framework, as well as the reports themselves,
obviously.  And it won't be something like scheme with such a high
"impedence mismatch" with C.  Options at that point are the obvious
ones: perl, ruby, python, maybe lua if we squint hard enough.  It'll be
an interesting dev discussion.

-- 
...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: 189 bytes
Desc: This is a digitally signed message part
Url : http://lists.gnucash.org/pipermail/gnucash-user/attachments/20070306/279dae28/attachment.bin