blfs wrote:
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.
--
Neil Williams ============= http://www.codehelp.co.uk/ http://www.dclug.org.uk/ http://www.isbn.org.uk/ http://sourceforge.net/projects/isbnsearch/
http://www.biglumber.com/x/web?qs=0x8801094A28BCB3E3
signature.asc
Description: OpenPGP digital signature
_______________________________________________ gnucash-devel mailing list [EMAIL PROTECTED] https://lists.gnucash.org/mailman/listinfo/gnucash-devel
