Am Montag, 3. September 2007 20:16 schrieb Daniel Espinosa:
> > On the other hand, the resulting format character itself is probably only
> > needed inside the gnucash/gncqof implementation and doesn't have to be
> > exposed to outside applications. Hence, in the long term this test
> > probably should have to be done by your external application, and in
> > gnucash this #ifdef check should be moved to an internal header file.
> > Well, that's a long-term goal.
>
> Scanf is used in file backend and other places inside GnuCash, then
> this tests,  I think, could be hide at the eyes of other applications
> and just expose the usefull API for other applications.

Yes. Derek and I already agreed on this.

> Why is a long-term goal?

Because it's not important for *gnucash*, hence it isn't a short-term goal 
*for gnucash*.

> Is it represent too much work?

Yes. Unless you send in a patch - feel free to do so.

> When will GC clean up this issues to make easy other applications to
> use its data, may be to 2.4 or 3.0?

No idea.

Christian
_______________________________________________
gnucash-devel mailing list
gnucash-devel@gnucash.org
https://lists.gnucash.org/mailman/listinfo/gnucash-devel

Reply via email to