On Fri, Oct 16, 2009 at 7:56 AM, Paul Moore <[email protected]> wrote: > Blast, I missed that. Thanks. That's probably because this code was > last checked before the stricter stack checking came in, and one of > the warnings I was ignoring wasn't as irrelevant as I'd thought... >
Yup. When you first wrote that code, Factor reported inference failures as compiler warnings and the word would continue to work. This is not the case anymore, the language is stricter now. This has improved performance and robustness. Keep an eye out for the error bar at the bottom and learn what all the different inference errors mean. The error list tool also reports unit test failures, help lint failures, and other things, so its handy. Slava ------------------------------------------------------------------------------ Come build with us! The BlackBerry(R) Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9 - 12, 2009. Register now! http://p.sf.net/sfu/devconference _______________________________________________ Factor-talk mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/factor-talk
