Installer using InnoSetup

[Christian Schulte]

Just for your info: taking the algorithms from Gecode to Mozart is almost
impossible (unless you completely rewrite). This is due to the fact that
Mozart's CPI is quite limited compared to Gecode (no incremental
propagation, only idempotent propagators supported, no staging, eager
fixpoint computation, etc).

Christian

--
Christian Schulte, http://www.imit.kth.se/~schulte/ 

-----Original Message-----
From: hackers-bounces at mozart-oz.org [mailto:hackers-bounces at mozart-oz.org]
On Behalf Of Filip Konvicka
Sent: Monday, February 13, 2006 1:12 PM
To: hackers at mozart-oz.org
Subject: Re: Installer using InnoSetup


 > If you can mail it, then I suggest you try mailing it to
 > kevin.glynn at gmail.com and I will put it somewhere and announce to the  >
hackers list.

OK, I'll send it.

 > Of course,  we need to consider your proposed changes before we freeze  >
1.3.2. Are they all covered by entries in the bug database?

Yes, both of these are in the bug database ('incoming' directory).

As for the Winsock issue, I still had some problems even with the 
#define FD_SETSIZE 1024 setting in wsock.hh, but everything is fine 
since I raised the limit to 10240.

For the edge finder/task intervals, I think that they are still far from 
perfect. It would be great if the Gecode's versions could be used (they 
use more recent algorithms and I think that they're much more powerful). 
But that's probably beyond 1.3.2, right? :-)

Cheers,
Filip

____________________________________________________________________________
_____
mozart-hackers mailing list
mozart-hackers at ps.uni-sb.de      
http://www.mozart-oz.org/mailman/listinfo/mozart-hackers