On Wed, Aug 08, 2012 at 10:53:47AM -0400, Rafael Schloming wrote: > The extra compiler checking you get with the enums is kind of nice from an > API perspective. What exactly is the problem with enum values in the > contracts?
You can't declare a check against an enum value for an API. So we can't leverage swig's contract feature to ensure that Ruby, for example, doesn't try to pass a different value or type for such an API. To quote their documentation: "Regrettably, there is no automatic way to perform similar checks with enums values. Maybe in a future release." -- Darryl L. Pierce, Sr. Software Engineer @ Red Hat, Inc. Delivering value year after year. Red Hat ranks #1 in value among software vendors. http://www.redhat.com/promo/vendor/
pgpfzTfHI8lGd.pgp
Description: PGP signature
