Sylvain,
I'll attempt to gin something up tomorrow. Thanks!
-Dave
On Sun, Jul 3, 2016 at 5:01 AM, Sylvain Munaut <[email protected]> wrote:
> Hi,
>
> > It's always
> > something that's not quite 100% right in my C++ code, but it's seriously
> > painful to debug as I have to resort to commenting code out and trying
> again
> > over and over.
>
> SWIG doesn't even look at the C++ source code, only the public headers.
>
>
> > Is there a way to have SWIG tell you that something is
> > messed up instead of pretending all is well?
>
> If the input to swig is invalid, it will report it as invalid.
> If it didn't then that means that what it received was valid ... it
> might not have been what you intended, but it's valid.
>
>
> So please provide a _specific_ example OOT tree that has "messed up"
> and the fix you had to do.
>
> Cheers,
>
> Sylvain
>
_______________________________________________
Discuss-gnuradio mailing list
[email protected]
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
