[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference clt::fuse

Title:	DEC FUSE - UNIX SDE
Notice:	See note #4 for kit locations
Moderator:	TLE::TALCOTT

Created:	Tue Oct 30 1990
Last Modified:	Fri May 23 1997
Last Successful Update:	Fri Jun 06 1997
Number of topics:	1276
Total number of notes:	4364

1262.0. "fortran with c directives" by RTOMS::PARETIJ () Mon Mar 03 1997 13:04

I don't seem  to be able to use the graph browser on a fortran
code that has c directives in it.

(I am using fuse 3.1 on digital unix 4 )

Thanks for any advice 

/ Joseph

T.R	Title	User	Personal Name	Date	Lines
1262.1	More info is requested	TLE::GOODRICH	Disconnecting odometers is dumb	`Mon Mar 03 1997 16:52`	14
	By C directives do you mean #if and #define directives? If so, then by convention the file type must be .F in order for the FUSE scanner to pass the file to the cpp program before it attempts to scan the Fortran code. Do your sources have the .F file type? Also, which DEC Fortran compiler do you use? If you have F90 installed, FUSE will attempt to do all the cross-referencing using the builtin FUSE support in the f90 compiler. Otherwise, FUSE uses its own Fortran scanner to find the cross-reference data. If you could supply some examples source files that are not being properly scanned, and how you specified the configuration target to the Call Graph Browser, we may be able to figure out what the problem is.
1262.2	f77 instead of f90 ?	RTOMS::PARETIJ		`Tue Mar 04 1997 06:13`	10
	OK ; converting from .f to .F helped alot but not all subroutines I expect get displayed in the graph browser. Perhaps it has to do with f90 (which is not what I want for this program ) Warning: /work2/tuebingen/dec/ns/UTIL/OMEX/omext.f, line 48: Bad # preprocessor line #include "params.fh" How can I use f77 instead of f90 ?
1262.3	You can force FUSE to use its own Fortran 77 scanner	TLE::GOODRICH	Mark Goodrich	`Tue Mar 04 1997 11:17`	18
	If you have f90 installed (i.e. /bin/f90 is present), then FUSE will invoke it with the -fuse_xref option to scan all your Fortran (.f, .F, .f90) sources. Since DEC Fortran 90 is supposed to be able to handle both f77 and f90 sources, there should be no problem in using it to scan your f77 source. However, if you want to use the FUSE Fortran scanner (which really only understands f77 not f90 source), you need to add the following override in a target-specific .xrefrc file: FORTRAN_COMMAND: $FUSE_BIN/fortran_scanner -b -fortran You can create a target-specific .xrefrc file by pressing on the "Edit .xrefrc" pushbutton in the Transcript window that contains the log of the scanning messages you should see when you first bring up the Call Graph Browser.