Intel® Fortran Compiler
Build applications that can scale for the future with optimized code designed for Intel® Xeon® and compatible processors.
Announcements
FPGA community forums and blogs on community.intel.com are migrating to the new Altera Community and are read-only. For urgent support needs during this transition, please visit the FPGA Design Resources page or contact an Altera Authorized Distributor.
29281 Discussions

Regarding array bound...

brb36641
Beginner
‎03-29-2006 02:58 PM
449 Views
Hello, deficuld error make me unhappy for longtime.
My program sometime failed by array bound error. Now I survey reason.
Therefore, I want to imprement error exception for array bound.
What is recomend?
If someone have some recomends, please let me know these.
It is convenience for mewhat is like"on error" in Visual basic.
0 Kudos

Link Copied

1 Reply
Steven_L_Intel1
Employee
‎03-29-2006 06:58 PM
449 Views
I don't know if you can do anything useful when an array bounds error occurs. There is a chapter on error handling in the Intel Visual Fortran Building Applications manual that may be helpful, but what do you want to do if such an error occurs?

If what you want to do is find out where in the program the error happens, simply run the program in the debugger. It will stop at the right place. Be sure you are using a current version of the compiler (9.0.030 is the latest) because some earlier versions didn't let the debugger see where the error occurred.
0 Kudos
Copy link
Reply

Community support is provided Monday to Friday. Other contact methods are available here.

Intel does not verify all solutions, including but not limited to any file transfers that may appear in this community. Accordingly, Intel disclaims all express and implied warranties, including without limitation, the implied warranties of merchantability, fitness for a particular purpose, and non-infringement, as well as any warranty arising from course of performance, course of dealing, or usage in trade.

For more complete information about compiler optimizations, see our Optimization Notice.