Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.2 9/18/84; site noscvax.UUCP
Path: utzoo!linus!decvax!ittatc!dcdwest!sdcsvax!noscvax!ogasawar
From: ogasawar@noscvax.UUCP (Todd H. Ogasawara)
Newsgroups: net.lang.c
Subject: Re: When words are good and when words are bad
Message-ID: <1050@noscvax.UUCP>
Date: Mon, 5-Aug-85 17:31:15 EDT
Article-I.D.: noscvax.1050
Posted: Mon Aug  5 17:31:15 1985
Date-Received: Wed, 7-Aug-85 03:14:40 EDT
References: <1985@ukma.UUCP> <2903@ncsu.UUCP> <527@oliveb.UUCP>
Reply-To: ogasawar@cod.UUCP (Todd H. ogasawara)
Organization: Naval Ocean Systems Center, San Diego
Lines: 20
Summary: 

In article <527@oliveb.UUCP> long@oliveb.UUCP (Dave Long) writes:
>In article <2903@ncsu.UUCP> mauney@ncsu.UUCP (Jon Mauney) writes:
>| If symbols are so great, why not do away with keywords entirely?  We could
>| use <- for "goto", @-> for "if", >< for "while", and [->] for "switch".
>| Wouldn't that make programs a lot easier to read?

Sounds like you might want to try APL.  Most people say that APl is harder
to read that other kinds of programming language.  However, if you keep
in mind that one line of APL is often the equivalent of dozens or hundreds
of lines of other high level lanaguages, it doesn't seem to bad..todd

p.s.  Let's not start an argument about the relative merits of C and APL.
  Both have their place in my software toolkit.  Sometimes one is more
  appropriate, sometimes the other is.

Todd Ogasawara, Computer Sciences Corp.
NOSC-Hawaii Laboratories

UUCPmail: {akgua,allegra,decvax,ihnp4,ucbvax}!sdcsvax!noscvax!ogasawar
MILNET:   OGASAWAR@NOSC