[gecode-users] new IntArgs fails

[Christian Schulte]

If you are interested in Python, you might want to check out Numberjack:
	http://4c110.ucc.ie/numberjack/home

We are in the process of providing an interface to Numberjack (trying to,
that is).

Christian

--
Christian Schulte, www.ict.kth.se/~cschulte/


-----Original Message-----
From: users-bounces at gecode.org [mailto:users-bounces at gecode.org] On Behalf
Of Denys Duchier
Sent: Monday, October 19, 2009 6:22 PM
To: users at gecode.org
Subject: Re: [gecode-users] new IntArgs fails

"Christian Schulte" <cschulte at kth.se> writes:

> Argument arrays are really meant to just pass arguments, they are bad as
> general data structures. Why not use vector instead?

I was playing with generating gecode bindings for python (to better
understand the issue, the options, and where the problems are) and
e.g. the constructor IntSet(IntArgs&) requires IntArgs; vector<int> is
not an option.  The generated wrapper for IntArgs does a new and that
didn't compile; I was simply curious if that was intended.

I, of course, don't particularly want IntArgs in python.  That was just
a quick try to see how some things worked out (or not).

Cheers,

--Denys

_______________________________________________
Gecode users mailing list
users at gecode.org
https://www.gecode.org/mailman/listinfo/gecode-users