About Constraint_System::has_strict_inequalities().
The method bool Constraint_System::has_strict_inequalities() const; is declared private. Probably, when it was first introduced, there were good reason to do so. However, I no longer see these reasons (maybe the initial specification has been improved and now it is "clean" also for the user). Moreover, there are occasions where this method might come handy for the user of the library and for the developers of library classes that are not friend of Constraint_System. So the question is: do you see any reason justifying the access restriction for this method? Note that, at the implementation level, we correctly disregard low-level constraints such as 0 <= eps <= 1. Ciao, Enea.
Enea Zaffanella wrote:
The method
bool Constraint_System::has_strict_inequalities() const;
is declared private. Probably, when it was first introduced, there were good reason to do so. However, I no longer see these reasons (maybe the initial specification has been improved and now it is "clean" also for the user). Moreover, there are occasions where this method might come handy for the user of the library and for the developers of library classes that are not friend of Constraint_System.
So the question is: do you see any reason justifying the access restriction for this method?
No, I think you can remove the access restriction.
Note that, at the implementation level, we correctly disregard low-level constraints such as 0 <= eps <= 1.
OK. Ciao, Roberto -- Prof. Roberto Bagnara Computer Science Group Department of Mathematics, University of Parma, Italy http://www.cs.unipr.it/~bagnara/ mailto:bagnara@cs.unipr.it
participants (2)
-
Enea Zaffanella -
Roberto Bagnara