[gecode-users] ES_NOFIX and ES_FIX
Christian Schulte
cschulte at kth.se
Tue May 6 17:55:27 CEST 2008
Hi, you are so damn right. Fixed in the trunk.
Christian
--
Christian Schulte, www.ict.kth.se/~cschulte/
-----Original Message-----
From: users-bounces at gecode.org [mailto:users-bounces at gecode.org] On Behalf
Of David Rijsman
Sent: Tuesday, May 06, 2008 4:56 PM
To: users at gecode.org
Subject: [gecode-users] ES_NOFIX and ES_FIX
Like to give you a heads up on a mistake in the documentation (I
hope). The documentation of Propagator::advise says the following:
....
A propagator must specialize this advise function, if it uses
advisors. The advise function must return an execution status as
follows:
ES_FAILED: the advisor has detected failure
ES_NOFIX: the advisor's propagator (that is, this propagator) does not
need to be run
ES_FIX: the advisor's propagator (that is, this propagator) must be run
....
I think the ES_NOFIX and ES_FIX are mixed up, it should be
ES_NOFIX: the advisor's propagator (that is, this propagator) must be run
ES_FIX: the advisor's propagator (that is, this propagator) does not
need to be run
Can you confirm this?
David
_______________________________________________
Gecode users mailing list
users at gecode.org
https://www.gecode.org/mailman/listinfo/gecode-users
More information about the gecode-users
mailing list