Compaq visual fortran 6.63/9/2024 ![]() ![]() ![]() Other internal error conditions (file open, read/write, etc.) would also call the universal debug assist routine prior to dumping the error message. This will give the user at least some means to better diagnose a problem. would all call the null function (with user break point) prior to mucking things in taking the program abort. It would be nice if STOP, _DOMAIN error, etc. code in 3rd party library) contains a STOP statement. Of particular annoyance is when a programmer (e.g. before the runtime systems nests down 10 levels into an error dump messaging system). The technique would be to provide a breakpoint symbol name of a null functionon which a user could place a break point and catch such problems early on (i.e. This is a relatively simple proceedure, which may be present, but not documented or easily found in the documentation. It would be nice if Intel and the other compiler an library writers would follow and documenta common programming practice that will aid the programmer in diagnosing such problems such as 'function': _DOMAIN error, and other program AB-END situations. I hope Steve or others at Intel will read my comments regarding this issue. ![]()
0 Comments
Leave a Reply.AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |