Well poop. I can't remember what was causing the issues (it was about a month ago). If I run across it again I'll copy off the code before fixing it so that I can show it here.
On Sun, Jul 3, 2016 at 5:59 PM, Dave NotTelling <dmp250...@gmail.com> wrote: > Sylvain, > > I'll attempt to gin something up tomorrow. Thanks! > > -Dave > > On Sun, Jul 3, 2016 at 5:01 AM, Sylvain Munaut <246...@gmail.com> 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 Discuss-gnuradio@gnu.org https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
