93 The tutorial is aimed at programmers learning how to develop applications with ECLiPSe and tries to codify a 'best practice'\index{best practice} for developers. It assumes a basic familarity with concepts of constraint and logic programming and is not a reference manual, so many concepts and language elements are only introduced very briefly. The material also includes some general topics from software engineering. Knowledge of general OO-related methodologies may be helpful to put that material into context.
1071 \index{best and rest}This concept is an extension of the minimum concept. It not only returns the best element in the input list, but also the rest of the original list without the best element. This rest can then be used for example to select another element, and so on.
1085             best(X,In1,Out1,In2,Out2)
1088 best(X,Y,X,L,[Y|L]):-
1091 best(X,Y,Y,L,[X|L]).
1096 If several elements of the list have the same best value, only the first one is selected. 
1782 The best way of finding failures is by code inspection, helped by logging messages which indicate the general area of the failure. If this turns out to be too complex, we may have to use the tracer.
1857 Lacking this formal approach, the best hope of checking correctness of a program lies in exercising it with different types of tests.
1894 \item It encourages ``best practice''\index{best practice} in the ECLiPSe application development, bringing together experts from different application teams.
2026 it is best not to leave blank lines between the clauses of a predicate

Indexes created Tue Jul 09 22:07:09 MDT 2024