As you see, not really agreement among us ;-) Somehow, we try to avoid silent failure as this is something that is difficult to track. But on the other hand, for automatically generated tables this might actually be the intended behavior.
Christian -- Christian Schulte, www.it.kth.se/~cschulte/ -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Mikael Zayenz Lagerkvist Sent: Tuesday, March 10, 2009 8:16 AM To: Malcolm Ryan Cc: gecode list Subject: Re: [gecode-users] Finalizing TupleSets On Tue, Mar 10, 2009 at 2:20 AM, Malcolm Ryan <[email protected]> wrote: > On 09/03/2009, at 8:55 PM, Christian Schulte wrote: >> The attempt to finalize an empty tuple set will also throw an >> exception but >> most likely only in 3.0.1 and not 3.0.0. > > Is that the intended behaviour? Having an empty tuple set seems > perfectly legitimate to me. An empty TupleSet is not a meaningful object to use for a constraint, since it would mean direct failure. Cheers, Mikael -- Mikael Zayenz Lagerkvist, http://www.ict.kth.se/~zayenz/ _______________________________________________ Gecode users mailing list [email protected] https://www.gecode.org/mailman/listinfo/gecode-users _______________________________________________ Gecode users mailing list [email protected] https://www.gecode.org/mailman/listinfo/gecode-users
