Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!seismo!rutgers!ames!ucbcad!ucbvax!sdcsvax!sdchem!tps
From: tps@sdchem.UUCP (Tom Stockfisch)
Newsgroups: comp.lang.fortran
Subject: Re: lex and ratfor
Message-ID: <651@sdchema.sdchem.UUCP>
Date: Wed, 18-Mar-87 02:14:18 EST
Article-I.D.: sdchema.651
Posted: Wed Mar 18 02:14:18 1987
Date-Received: Thu, 19-Mar-87 05:33:36 EST
References: <2133@alvin.mcnc.UUCP>
Sender: news@sdchem.UUCP
Reply-To: tps@sdchemf.UUCP (Tom Stockfisch)
Organization: UC San Diego
Lines: 19
Keywords: lex, ratfor, f77, help

In article <2133@alvin.mcnc.UUCP> kenkel@mcnc.UUCP (Stephen Kenkel) writes:

>  Has anyone gotten lex working with ratfor?  The documentation claims
>  that -r produced ratfor output.  A quick try looks unpromising,
>  lex is generating things like yylval.ival which ratfor cannot understand.

"yylval" is used in yacc, and shouldn't even appear in a lex-only program.
Are you using yacc as well?  If so, you're "stuck" with using C.

>  (The application is a program which MUST be written in FORTRAN, and 
>  needs a decent parser)

Does ALL of the program have to be written in fortran?  It is not hard on
most systems to mix fortran with C, especially if their tasks are well
separated (like parsing (C) and number crunching (fortran)).  Although,
it is better if the C portion does all or most all of the i/o.

|| Tom Stockfisch, UCSD Chemistry	tps%chem@sdcsvax.ucsd.edu
					or  sdcsvax!sdchem!tps