--- James Gray <[EMAIL PROTECTED]> wrote: > Greg, > In the best of all possible worlds, where do the business rules > belong in a > Mumps/Fileman system? > > Jim Gray > I don't think there's any one answer. You can write routines containing code that implements business rules, or you can create files containing the necessary data. You can implement a message based system (either literally with TCP/IP, or logically in your MUMPS code), but the point is to be consistent, and to try and stick to the idea that each piece of code is designed to play a specific role. There's a word for this: it's called cohesion. Code with a high degree of cohesion usually tends not to be highly coupled (or as people sometimes say, is not spaghetti code), but cohesion and coupling are really separate concepts. When code ends up being highly coupled (as is the case with much of VistA), that is almost always a sign of poor cohesion.
=== Gregory Woodhouse <[EMAIL PROTECTED]> "All truth passes through three stages: First, it is ridiculed. Second, it is violently opposed. Third, it is accepted as being self-evident." --Arthur Schopenhauer ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642 _______________________________________________ Hardhats-members mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/hardhats-members
