Hi all, I made a minor change to the deploy tool, after Ben Schlingelhof's feedback. If you bump the reflection support to Level 4 (Debugger) or higher, then the deploy tool actually uses the debugger. So if you have a typo in your source file you're deploying, instead of getting an incomprehensible FEP you get a nice error message just like you would in the listener. This goes for runtime errors too; if the debugger is included in the deployed image, then your main word is wrapped in a 'try'. If you elect to strip out the debugger by setting reflection to level 3 or lower, then you still get nasty FEP errors, but one approach would be to debug your program with a high reflection level then bring it down when you're ready to do some final testing and you want the smallest possible image size.
I also fixed a bug I noticed; if the reflection level is set to 5 (Parser) then the parser didn't actually work, it would only work at level 6. Slava ------------------------------------------------------------------------------ Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, CA -OSBC tackles the biggest issue in open source: Open Sourcing the Enterprise -Strategies to boost innovation and cut costs with open source participation -Receive a $600 discount off the registration fee with the source code: SFAD http://p.sf.net/sfu/XcvMzF8H _______________________________________________ Factor-talk mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/factor-talk
