Path: utzoo!attcan!uunet!pyrdc!pyrnj!rutgers!cmcl2!phri!roy
From: roy@phri.UUCP (Roy Smith)
Newsgroups: comp.lang.fortran
Subject: Re: Fortran vs C for computations (compiler vs. editor macros)
Message-ID: <3462@phri.UUCP>
Date: 7 Sep 88 11:44:20 GMT
References: <1443@valhalla.ee.rochester.edu> <3256@lanl.gov>
Reply-To: roy@phri.UUCP (Roy Smith)
Organization: Public Health Research Inst. (NY, NY)
Lines: 21

In article <3256@lanl.gov> jlg@lanl.gov (Jim Giles) writes:
> C makes macros part of the language definition instead of part of the
> text editing environment (where it belongs).

	Not in my book.  I've got available to me both C's #define macros
and emacs macros (word abrev mode, and more complex stuff).  I suppose I
could make emacs expand "c = getc (fp);" into

c = (--(fp)->_cnt>=0? (int)(*(unsigned char*)(fp)->_ptr++):_filbuf(fp));

if I wanted to, but why would I want to?

	Hey, I agree, there are a lot of things you can do in Fortran just
as well as in C, if not better (complex arithmetic, for example), but if
you're going to knock C, at least pick on one of its real faults.  It has
enough of them; no need to invent more.
-- 
Roy Smith, System Administrator
Public Health Research Institute
{allegra,philabs,cmcl2,rutgers}!phri!roy -or- phri!roy@uunet.uu.net
"The connector is the network"