Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!wuarchive!zaphod.mps.ohio-state.edu!swrinde!ucsd!ames!skipper!elxsi!maine From: maine@elxsi.dfrf.nasa.gov (Richard Maine) Newsgroups: comp.lang.fortran Subject: Re: WRITE don't do that too me! Message-ID: Date: 11 Sep 90 21:32:59 GMT References: <13812@smoke.BRL.MIL> Sender: news@skipper.dfrf.nasa.gov Distribution: comp Organization: NASA Dryden, Edwards, Cal. Lines: 48 In-reply-to: chidsey@smoke.BRL.MIL's message of 11 Sep 90 14:58:08 GMT On 11 Sep 90 14:58:08 GMT, chidsey@smoke.BRL.MIL (Irving Chidsey) said: Irving> In article quan@sol.surv.utas.oz (Stephen Quan).. Stephen> how can I suppress the NEWLINE character?... Stephen> At the moment, the only solution I can see is to store the codes Stephen> into a string of some kind and output the string when a NEWLINE would Stephen> be safe to output. That's a very good and safe approach. It is also likely to be good for efficiency. On many operating systems, something about like that happens anyway, though it may be "behind your back". Irving> No NEWLINE is an extension to the standard. On our Convex a $ Irving> is what supresses NEWLINEs. As Irving says, it is an extension. It is a fairly common one, but not universal by any means. Note that Fortran 90 does include a simillar concept as standard. (It's called non-advancing I/O there). Stephen> Does the standard insist on uppercase characters? Irving> lower case is also an extension to the standard. I believe it is Irving> a popular extension. The standard allows only one case (usually interpreted as upper case, though it's not quite explicitly stated). However, allowing both cases is an extension so common as to be almost universal. The only exceptions I have seen for a long time have been on machines that don't have both cases in their hardware character set. The process of transferring ASCII (or EBCDIC) source code to such machines usually handles the case conversion automatically anyway. Thus it's awfully hard to get in trouble using mixed case as long as you do not use the C abomination (oops, sorry about the religion) of using case to distinguish otherwise identically spelled variables. Note here also that mixed case is "sanctioned" by the Fortran 90 standard. It is not required that all compilers support two cases (hard to do on systems with 6 bit characters), but it is sanctioned. The Fortran 90 standard specifies that two variable names differing only in case refer to the same variable. (I'm paraphrasing here). -- -- Richard Maine maine@elxsi.dfrf.nasa.gov [130.134.64.6]