[gecode-users] Space access during ViewSelection?

Martin Mann mmann at informatik.uni-freiburg.de
Tue Jul 11 18:07:12 CEST 2006


for me a const access is enough! (anyway better than static variables)

also const makes sense for me, because it should be possible to get 
further informations but not to change the space..

is there any schedule for publication the changed interface?

and maybe the same (space access) would be nice for view-selection too!?

thanks

Martin



Christian Schulte schrieb:
> Hmmm, I just had a look and it is not so obvious: would it be okay if the
> space would be passed as const? What does make more sense in this situation
> (I think const: because one should be able to ask the same space multiply
> for a description and always get the same description).
> 
> Anyway, we are going to change the interface of branchings and branchin
> descriptions anyway: we decided to make branching descriptions mandatory
> given the huge importance they carry for efficient recomputation. This
> allows us to make the interfaces considerably simpler.
> 
> Christian
> 
> --
> Christian Schulte, http://www.imit.kth.se/~schulte/ 
> 
> -----Original Message-----
> From: users-bounces at gecode.org [mailto:users-bounces at gecode.org] On Behalf
> Of Christian Schulte
> Sent: Tuesday, July 11, 2006 3:51 PM
> To: 'Martin Mann'; 'gecode user list'
> Subject: RE: [gecode-users] Space access during ViewSelection?
> 
> 
> That's okay. We will do that anytime soon.
> 
> Christian
> 
> --
> Christian Schulte, http://www.imit.kth.se/~schulte/ 
> 
> -----Original Message-----
> From: users-bounces at gecode.org [mailto:users-bounces at gecode.org] On Behalf
> Of Martin Mann
> Sent: Tuesday, July 11, 2006 3:40 PM
> To: gecode user list
> Subject: [gecode-users] Space access during ViewSelection?
> 
> 
> ;)
> 
> the next ugly question is waiting:
> 
> This time I m fighting with value selection classes for my branching. In 
> a function "int val(IntView &x)" the value to split on of the domain x 
> is determined.
> 
> I would like to have access to the "father" Space of x...
> 
> The reason is the usage of some further informations out of Space, to 
> select the value.
> Am I the only one who is interested in doing such things or may it be 
> interesting for others too? If that's the case may it be possible to add 
> the calling Space to the parameter list of "val(..)" in general? (I know 
> this would lead to some changes in the code.. and to incompatibilities 
> with user defined value selections for older versions of gecode..)
> 
> Otherwise i ve got to do some static stuff I dont like, but that will do 
> it for the moment.
> 
> Thanks for thinking about
> 
> Martin
> 
> _______________________________________________
> Gecode users mailing list
> users at gecode.org https://www.gecode.org/mailman/listinfo/gecode-users
> 
> 
> _______________________________________________
> Gecode users mailing list
> users at gecode.org https://www.gecode.org/mailman/listinfo/gecode-users
> 
> 




More information about the gecode-users mailing list