Ulrich Scholz wrote: > > > PS. Two small comments: The explanation of "++X" in the Terminology section > of the User Manual has a bug. And I consider the explanation of the > creation of dynamic solver instances confusing: Maybe you should mention > that to reuse the atom (e.g., the one unified with Pool in the second > example of 9.3.2) you need to use eplex_cleanup/0. ++X: Thanks for pointing out the typo. I have corrected it (in the 6.0 branch). Solver instances: I am not sure what exactly you mean by `reuse of the atom'. You normally don't need to use eplex_cleanup, unless you want to destroy the existing instance in a non-logical way, i.e. if you want to solve a new problem using the same eplex instance before you backtrack over the original instance. I would strongly recommend you to use a different eplex instance in such cases. Secondly, the recommended way of using eplex instances are to declare them statically using a directive, as stated in the documentation. You should avoid creating eplex instances dynamically (as in the example of 9.3.2 you cite above), and certainly to avoid creating a large number of such eplex instances. Each instance is an ECLiPSe module, and is relatively expensive in terms of resources used. Cheers, Kish -- This e-mail may contain confidential and privileged material for the sole use of the intended recipient. Any review, use, distribution or disclosure by others is strictly prohibited. If you are not the intended recipient (or authorized to receive for the recipient), please contact the sender by reply e-mail and delete all copies of this message. Cisco Systems Limited (Company Number: 02558939), is registered in England and Wales with its registered office at 1 Callaghan Square, Cardiff, South Glamorgan CF10 5BT.Received on Mon Sep 15 2008 - 08:02:16 CEST
This archive was generated by hypermail 2.2.0 : Thu Feb 02 2012 - 02:31:58 CET