No - there's no additional compile step I'm aware of... You're forced to use 'best practices' to optimize a program - but if you compile a routine with UniData's Profiler Option 'on', the really interesting thing is that you can see where the system is spending a lot of time, or doing a lot of recursion - you can see clock time spent, CPU time spent, and number of times the subroutine was called. I found it immensely useful to find areas of programs I could optimize further to get the most 'bang for my buck' - it also led me to find a subroutine I called many times that had a file open within it - by fixing that one issue, I saved 30% on one routine... YMMV...
David W. -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Raymond de Bourbon Sent: Friday, March 19, 2004 8:39 AM To: 'U2 Users' Subject: Unidata "Flashbasic" Does Unidata have an option similar to D3 that enables one to "Flashcompile" a basic program into native machine code? I have a program that I need to squeeze the optimal performance out of.. Regards Raymond de Bourbon -- u2-users mailing list [EMAIL PROTECTED] http://www.oliver.com/mailman/listinfo/u2-users -- u2-users mailing list [EMAIL PROTECTED] http://www.oliver.com/mailman/listinfo/u2-users
