From maine@altair.dfrc.nasa.gov  Wed Dec  4 20:50:13 1996
Received: from altair.dfrc.nasa.gov ([130.134.34.72]) by dkuug.dk (8.6.12/8.6.12) with ESMTP id UAA18389 for <sc22wg5@dkuug.dk>; Wed, 4 Dec 1996 20:50:09 +0100
Received: by altair.dfrc.nasa.gov (SMI-8.6/SMI-SVR4)
	id LAA01936; Wed, 4 Dec 1996 11:49:53 -0800
Date: Wed, 4 Dec 1996 11:49:53 -0800
Message-Id: <199612041949.LAA01936@altair.dfrc.nasa.gov>
From: Richard Maine <maine@altair.dfrc.nasa.gov>
To: "Loren Meissner" <LPMeissner@msn.com>
Cc: sc22wg5@dkuug.dk
Subject: (SC22WG5.1214) More on Fortran subset
In-Reply-To: <199612041524.QAA14488@dkuug.dk>
References: <199612041524.QAA14488@dkuug.dk>
Mime-Version: 1.0 (generated by tm-edit 7.92)
Content-Type: text/plain; charset=US-ASCII

Loren Meissner writes:
 > Keep CONTINUE (?)

I would keep it.  Not as a DO terminator (always use END DO),
but I find it a useful place to "hang" labels for the few GOTOs
(or end= or err=).  In fact my personal style is to never GOTO
anything except a CONTINUE.  No real point in enforcing that style
preference, but I think its one that should be allowed.  Putting
a GOTO target label on an executable statement can complicate
maintenance when you discover that you want to add something
before the currently labelled statement.

 > Remove spacing control for line printers.

Yes.  I'm enthusiastically in favor of removing that from the
subset.  It causes no end of complaints and compatability
problems (different systems doing the carriage control in different
contexts).  I've personally adopted the practice of always
putting blank carriage control characters on every line meant
for output to the terminal.  I never use any other carriage control
character.  (If I want to skip a line, I just write a blank line).
This way, things work ok regardless of whether the carriage control
convention is applied or not - just means that everything is shifted
one space to the right in some/many cases, so I need to be sure to
stop at least 1 character short of the maximum expected terminal
width.  This is the only way I've found to be very portable, and
it seems sort of silly.

In fact, I'd also be in favor of adding a CARRIAGECONTROL="NONE" (or
some other spelling of the same concept) option to the full language.

--
Richard Maine
maine@altair.dfrc.nasa.gov

