Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!rutgers!cmcl2!ccnysci!sukenick
From: sukenick@ccnysci.UUCP (SYG)
Newsgroups: comp.lang.fortran
Subject: Re: CHARACTER EQUIVALENCE (Was Re: fortran to C converter)
Message-ID: <1747@ccnysci.UUCP>
Date: 26 Apr 89 17:23:10 GMT
References: <67044@pyramid.pyramid.com> <1390@hudson.acc.virginia.edu> <11538@cgl.ucsf.EDU>
Reply-To: sukenick@ccnysci.UUCP (SYG)
Organization: City College Of New York
Lines: 12

>to the nearest word, though.  That's probably what most implementations
>do;  I've never seen a compiler that enforced the no-mixing rule.

Try  the  PDP-11  f77  compiler.
It gets mad if you put mixed character and other types in common blocks;
but it doesnt mind  byte (a type extention) with integers, etc or if you
equivalence a character to another type.
But then again, it gets mad about a lot of things :-)

BTW, is it ok to compare characters with logical operators
eg: .or. .and. .gt. .lt.   or is it required that you use
the gt, lt, etc functions (77 & in 88)?