QOF code question?
neil at codehelp.co.uk
Thu Aug 26 14:32:16 EDT 2004
> What's so hard to understand?
> Sometimes automation (like diff) just can't do what you need and you
> have to involve the human to make some decisions about what gets
> changed and what doesn't.
> Should changes to one module require changes to another?
Sometimes. GnuCash and QOF are under continuous development. Sometimes
that means that an advance in one module is best implemented by using a
small adjustment to another module. Any particular object is only
written with the current design in mind, things can change and other
features may become desirable. A small change in one module can allow
large changes in the module that uses the new functionality. There's
absolutely no point in duplicating the function by keeping the new code
within an inappropriate module. It also makes the new function available
to other modules leading to a cascade of changes that bring new
functionality to a variety of parts of the program.
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 249 bytes
Desc: OpenPGP digital signature
Url : http://lists.gnucash.org/pipermail/gnucash-devel/attachments/20040826/7d3fab2e/signature.bin
More information about the gnucash-devel