Date: Fri, 31 Dec 1999 08:52:36 -0600 (CST) From: Gene Harris <zeus@tetronsoftware.com> To: cjclark@home.com Cc: FreeBSD Questions <freebsd-questions@FreeBSD.ORG> Subject: Re: Back to the FORTRAN Question Message-ID: <Pine.BSF.4.10.9912310843580.607-100000@tetron02.tetronsoftware.com> In-Reply-To: <199912132312.SAA74814@cc942873-a.ewndsr1.nj.home.com>
next in thread | previous in thread | raw e-mail | index | archive | help
A quick scan of "man f2c" turned up the option -E to declare all uninitialized common blocks as EXTERN. If you check in f2c.h, you'll see the appropriate declarations. I tried this on a small program block, and found the first time I used the include I needed to omit the -E option in the first file in which the include was used, otherwise, every object assumes the named common is external and it never gets declared. :-) I don't have time to check this on the gnu site, but I think there is a modifier you may include somewhere in the common block statement, such as ALIAS, or EXTERN. I just cannot remember. I have an old molecular orbital calculation program that I ported to f77/f2c and I ended up creating a dummy BLOCK DATA subprogram to contain all named commons. Then all other files referred to all named commons as external. Hope this helps, and sorry I am not clearer on the details. You may find more help on the gnu site. There used to be a FORTRAN mailing list, although I think that is dead and gone. HTH, Gene Harris On Mon, 13 Dec 1999, Crist J. Clark wrote: > My f2c FORTRAN problems are still haunting me (see thread 'FORTRAN > Error Question' from November). This time, however, I think I have > more of an idea what is going on. > [snip] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.4.10.9912310843580.607-100000>