Re: Problem with LUABIND_NO_ERROR_CHECKING
Daniel Wallin <[email protected]>
| Newsgroups | gmane.comp.lang.lua.bind.user |
|---|---|
| Message-ID | <[email protected]> |
Tony Kostanjsek wrote:
> hi,
>
> first of all: thanks for luabind 0.9, automatic smart pointer
> downcasts alone are brilliant, very much appreciated!
Thank you.
> Unfortunately, activating LUABIND_NO_ERROR_CHECKING doesn't work for
> me anymore and crashes the application. I had this buried in the release
> build, which I hadn't tried since luabind 0.8, and narrowed it down to
> the testcase you can find below. The test uses luabind 0.9 release from
> sourceforge (dated Jan 5th 2010), lua 5.1.4, boost 1.40, all statically
> linked, compiled using gcc 4.0 on Mac OS 10.5.
> The same happened in on 10.6 with gcc 4.2, 32 or 64 bit build didn't
> matter.
OK, seems like LUABIND_NO_ERROR_CHECKING is broken in 0.9. The problem
is that we have code like:
# ifndef LUABIND_NO_ERROR_CHECKING
if (converter.match(...) == -1)
{
// ... report failure
}
# endif
... converter.apply(...); // do actual conversion
This was fine in 0.8, but in 0.9 the conversion process has two stages,
the first being match(), so they have to be called in succession.
I suggest turning off LUABIND_NO_ERROR_CHECKING; it doesn't do very much
in 0.9 anyway.
--
Daniel Wallin
BoostPro Computing
http://www.boostpro.com
------------------------------------------------------------------------------
This SF.Net email is sponsored by the Verizon Developer Community
Take advantage of Verizon's best-in-class app development support
A streamlined, 14 day to market process makes app distribution fast and easy
Join now and get one step closer to millions of Verizon customers
http://p.sf.net/sfu/verizon-dev2dev