NO FRAMES

Macro ILOBARRIERCALLBACK0

Definition file: ilcplex/ilocplex.h

ILOBARRIERCALLBACK0(name)

ILOBARRIERCALLBACK1(name, type1, x1)

ILOBARRIERCALLBACK2(name, type1, x1, type2, x2)

ILOBARRIERCALLBACK3(name, type1, x1, type2, x2, type3, x3)

ILOBARRIERCALLBACK4(name, type1, x1, type2, x2, type3, x3, type4, x4)

ILOBARRIERCALLBACK5(name, type1, x1, type2, x2, type3, x3, type4, x4, type5, x5)

ILOBARRIERCALLBACK6(name, type1, x1, type2, x2, type3, x3, type4, x4, type5, x5, type6, x6)

ILOBARRIERCALLBACK7(name, type1, x1, type2, x2, type3, x3, type4, x4, type5, x5, type6, x6, type7, x7)

This macro creates two things: an implementation class for a user-defined callback named nameI and a function named name that creates an instance of this class and returns a handle for it, that is, an instance of IloCplex::Callback. This function needs to be called with an environment as its first parameter, followed by the n parameters specified at the macro execution in order to create a callback. You can then use the callback by passing it to the use method of an IloCplex object.

The class nameI that is created by the macro includes the implementation of method duplicateCallback as required for callbacks. The implementation of the main method must be provided in curly brackets {} by the user and must follow the macro invocation, like this:

 
 ILOBARRIERCALLBACKn(name, ...) {
 
 // implementation of the callback
 
 }

For the implementation of the callback, methods from the class IloCplex::BarrierCallbackI and its parent classes can be used.

You are not obliged to use this macro to define callbacks. When the macro seems too restrictive for your purposes, we recommend that you define a callback class directly. Since the argument name is used to name the callback class, it is not possible to use the same name for several callback definitions.

See Also: