Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!seismo!brl-adm!adm!MRC%PANDA@sumex-aim.stanford.edu
From: MRC%PANDA@sumex-aim.stanford.edu (Mark Crispin)
Newsgroups: comp.lang.c
Subject: palindromes
Message-ID: <2165@brl-adm.ARPA>
Date: Tue, 6-Jan-87 14:59:09 EST
Article-I.D.: brl-adm.2165
Posted: Tue Jan  6 14:59:09 1987
Date-Received: Tue, 6-Jan-87 22:59:21 EST
Sender: news@brl-adm.ARPA
Lines: 17


     Some of you may be interested to know that the C palindromes compile
and execute correctly with the DEC-20 C compiler, although there are
periodic warnings about nested comments during compilation (I think the
authors of the compiler thought it would be a useful feature to warn
about this).  So they are good examples of portable code.  The byte sizes
given of the programs with newlines were off by one for each newline, since
a DEC-20 ASCII file uses CRLF to express newline, not bare LF like Unix.

     So they are good examples of portable code.

     The usual way in which people writing C code lose with machine
independence is in having code that assumes that a byte, a small integer,
a pointer, and an address all have the same representation and are
interchangable.  One really awful dependency happened in Unix Logo; it
had code which knew in which direction machine stacks grew in memory!
-------