Path: utzoo!utgpu!jarvis.csri.toronto.edu!rutgers!apple!ames!lll-winken!uunet!cs.dal.ca!silvert
From: silvert@cs.dal.ca (Bill Silvert)
Newsgroups: comp.lang.fortran
Subject: Re: Fxref & Flink -- deficiencies?
Summary: FXREF handles some space problems
Message-ID: <1989Jul5.114157.15667@cs.dal.ca>
Date: 5 Jul 89 11:41:57 GMT
References: <1989Jul3.125106.27708@cs.dal.ca> <12112@pur-ee.UUCP>
Sender: silvert@cs.dal.ca.UUCP (Bill Silvert)
Reply-To: bill@biomel.UUCP
Organization: Habitat Ecology Div., Bedford Inst. of Oceanography
Lines: 26

In article <12112@pur-ee.UUCP> hankd@pur-ee.UUCP (Hank Dietz) writes:
>are all DO loop headers.  Yuck.  By the way, even fairly reasonable folk
>sometimes rely on spaces not being separators:
>
>	GO TO 10
>
>instead of:
>
>	GOTO 10

I found Dietz's comments very interesting, and I wanted to note that flink
and fxref do recognize some of the common variants, such as both GOTO and
GO TO, and both ENDIF and END IF.  They do not recognize unusual variants like
EN DIF, and spaces in variable names (e.g. HOT DOG) are not acceptable.

It would be nice if Fortran 8x accepted the _ as a character, which would 
also facilitate interfacing code in C and other languages.  I wish I had some
easy way to identify some subroutine names as being non-Fortran, since I often
have to call C and assembler routines to handle graphics, etc., and the ability
to use a leading _ (just as C uses a tailing _) would help.

-- 
Bill Silvert, Habitat Ecology Division.
Bedford Institute of Oceanography, Dartmouth, NS, Canada B2Y 4A2
	UUCP: ...!{uunet,watmath}!dalcs!biomel!bill
	Internet: biomel@cs.dal.CA	BITNET: bs%dalcs@dalac.BITNET