[gecode-users] Question on rewriting

[Christian Schulte]

Hi,

 

That should be fine, however I would not recommend it, really, for
efficiency reasons: when a propagator is being rewritten it is done such
that most likely no additional memory needs to be allocated for both the
newly created propagator and the subscriptions this propagator is going to
create. 

 

Then, the newly created propagator actually inherits some information from
the propagator being rewritten, such as id, failure count, etc. You would
have to make sure that this happens as well.

 

Cheers

Christian

 

--

Christian Schulte, www.gecode.org/~schulte

Professor of Computer Science, KTH,  <mailto:cschulte at kth.se>
cschulte at kth.se

Expert Researcher, RISE ICT/SICS,  <mailto:cschulte at sics.se>
cschulte at sics.se

 

From: users-bounces at gecode.org [mailto:users-bounces at gecode.org] On Behalf
Of Drescher, Conrad
Sent: Friday, March 10, 2017 09:30
To: users at gecode.org
Subject: [gecode-users] Question on rewriting

 

Hi there,

 

I have a question on rewriting during propagation as described in MPG. MPG
recommends you call the propagator post function of the constraint you’re
rewriting to. I wonder whether it’d be possible to use the constraint post
function, too. Of course, that might be less efficient. But I wonder
foremost about whether I’d break any of the propagator obligations.

 

Many thanks!

Conrad

 

Dr. Conrad Drescher

Senior Developer | Variant Configuration
P&I S/4HANA Idea – LoB Research & Development

SAP SE | Dietmar-Hopp-Allee 16 | 69190 Walldorf | Germany

T +49 6227 7-77888 | M +49 160 90684883 | E conrad.drescher at sap.com
 <http://www.sap.com/> www.sap.com


Please consider the impact on the environment before printing this e-mail.


Pflichtangaben/Mandatory Disclosure Statements: 
 <http://www.sap.com/company/legal/impressum.epx>
http://www.sap.com/company/legal/impressum.epx

Diese E-Mail kann Betriebs- oder Geschäftsgeheimnisse oder sonstige
vertrauliche Informationen enthalten. Sollten Sie diese E-Mail irrtümlich
erhalten haben, ist Ihnen eine Kenntnisnahme des Inhalts, eine
Vervielfältigung oder Weitergabe der E-Mail ausdrücklich untersagt. Bitte
benachrichtigen Sie uns und vernichten Sie die empfangene E-Mail. Vielen
Dank. 

This e-mail may contain trade secrets or privileged, undisclosed, or
otherwise confidential information. If you have received this e-mail in
error, you are hereby notified that any review, copying, or distribution of
it is strictly prohibited. Please inform us immediately and destroy the
original transmittal. Thank you for your cooperation.

 

 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.gecode.org/pipermail/users/attachments/20170313/656ece34/attachment-0001.html>