It is OK, it works very well :)
I prefered use and({ ... ]) instead of portfolio([ ... ]). It is more
closed what I want.
Thank you very much Guido :)
PS : It is a pity that the search combinators have not updated for
activity based search for example or default search :S
Best Regards,
Mohammed
I can't test it right now, but it should be like this:
portfolio([
%% minimise => obj1 < lv("best1")
%% maximize => obj1 > lv("best1")
and(
post(obj1 < lv("best1"),
and(s,assign(best1,obj1))
),
prune
),
%% minimise => obj2 < lv("best2")
%% maximize => obj2 > lv("best2")
and(
post(obj
