🚀 go-pugleaf

In article <1993Jan3.040453.20688@chpc.utexas.edu>, michael@chpc.utexas.edu (Michael Lemke) writes:
|> I'd rather think the *Unix* stuff should honor
|>FORTRAN carriage control.  Well, I know it doesn't but a PRINT
|>statement after all creates a print file (or even sends something to a
|>printer), so doesn't FORTRAN require print files to honor the carriage
|>control character?  What is the excuse this time that the Unix joke is
|>still standard conform?

They have put there a filter called asa, and you just pipe the output
through it.  But then you will have a bit of a problem for interactive
programs (buffering will be your enemy!), and also for "batch"
programs writing on a file if you like to peek at the output while the
program is running.

|>  BTW, in Sun Fortran there is a special STATUS='PRINT' in
|>the OPEN statement which causes the first character to be ignored if a
|>blank or to be converted to a CTRL/L if a 1 etc.  `+' does not work
|>though. This evne works for stdout but I don't know about PRINT.  Maybe 
|>your Unix compiler has something similar.

This sounds a neat idea and I wholeheartly suggest that all Unix compiler
writers put this feature in (hopefully, with the same syntax ...).  
I only have two questions: how can you OPEN the unit where the PRINTs
go (usually mapped to the Unix standard output) ?  OPEN(*,) ???
And, are you sure that the keyword is 'STATUS'? I think that STATUS
has another meaning associated with it and cannot be overloaded.

Thanks to all who replied to my original post.

furio
--
Furio Ercolessi
Materials Research Laboratory           |   Intl School for Advanced Studies
Univ. of Illinois at Urbana-Champaign   |   Trieste, Italy
furio@uiuc.edu                          |   furio@sissa.it