Is that for performans reasons or primarily understandability?
I'm building an app where the Java code constructs a very simple domain model that is asserted as a set of facts. The end user is then able to write ad-hoc rules, infering relationships that the app could never know in advance.
On Tue, 18 May 2004 10:16:43 -0700 (PDT), <[EMAIL PROTECTED]> wrote:
I think Simon Harris wrote:As a general rule (pardon the pun), what would you consider "better" form:
Always prefer unordered facts (those for which you defune an explicit deftemplate) over ordered ones. They will always be much more efficient, and code that uses them is generally easier to understand because of the slot names.
--------------------------------------------------------- Ernest Friedman-Hill Science and Engineering PSEs Phone: (925) 294-2154 Sandia National Labs FAX: (925) 294-2234 PO Box 969, MS 9012 [EMAIL PROTECTED] Livermore, CA 94550 http://herzberg.ca.sandia.gov
--------------------------------------------------------------------
To unsubscribe, send the words 'unsubscribe jess-users [EMAIL PROTECTED]'
in the BODY of a message to [EMAIL PROTECTED], NOT to the list
(use your own address!) List problems? Notify [EMAIL PROTECTED]
--------------------------------------------------------------------
-- Simon Harris RedHill Consulting, Pty. Ltd. 12/55-67 Batman Street West Melbourne VIC 3003 +61 417 505 611 http://www.redhillconsulting.com.au
-------------------------------------------------------------------- To unsubscribe, send the words 'unsubscribe jess-users [EMAIL PROTECTED]' in the BODY of a message to [EMAIL PROTECTED], NOT to the list (use your own address!) List problems? Notify [EMAIL PROTECTED] --------------------------------------------------------------------
