🚀 go-pugleaf

In article <45iqtj$83u@lyra.csx.cam.ac.uk>,
Nick Maclaren <nmm1@cus.cam.ac.uk> wrote:
|In article <451qot$lk6@tornews.torolab.ibm.com>, dmm@neutron.torolab.ibm.com (Dave Mooney) writes:
[snip]
||> An implementation could well define the end-of-line indicator to be "an
||> arbitrary number of spaces followed by a newline", so code that has those
||> trailing tabs and spaces is still conforming.  Note that this is how
||> implementations on record-oriented architectures like IBM big iron get
||> around the lack of a newline character.
|
|Actually, they use a different loophole in the standard, but I take your
|point.  If an implementation uses your escape, then either it has a major
|effect on the handling of text files during execution or it requires
                                             ^^^^^^^^^
					    compilation?
|different text file semantics for compilation and execution.  Either of
|those would be possible, if bizarre.

You must be too young to remember punched cards.  Would you have a
"non-bizarre" C implementation which accepts punched-card input require
that continuation "\" be placed in column 80?  I would consider *that*
requirement to be "bizarre!"

:-) of course.

Cheers,
Stan.
-- 
HELP!  I'M BEING HELD PRISONER IN A .SIGNATURE FACTORY!
    Stan Ryckman   sgr@alden.com