wmartin@ut-ngp.UUCP (03/11/87)
Has anyone else been having problems with the MacFortran "execute" statement? It seems to cause havoc with any program I use it in, especially when it's time to call a subroutine. Upon return from the subroutine (even if the call is >30 lines away from the "execute" statement) one or two of the program's variables will have their values trashed, i.e. garbaged. In the most recent case, I called a sub from inside a DO loop. The index of the DO loop was 1 upon calling the sub, and 52580 upon return. Upon removing the "execute" statement ~50 lines previous, the problem disappeared! Also, be advised that spurious "gremlin" characters appearing in your source file will thoroughly confuse the Fortran compiler. One instance of this occurred when I used the MockWrite desk accessory to edit a pro- gram. For some reason, accidentally hitting the "Enter" key in my version of MockWrite will insert a Ctrl-C in the text at the insertion point. With a Ctrl-C imbedded in your source (of course it is invisisble to your editor) the compiler will freak out and give all sorts of error messages for no apparent reason. If this happens, use FEdit to search through your code, or some text editor that "shows invisibles", to remove non-alpha chars from the file. -w