Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.2 9/18/84; site brl-tgr.ARPA
Path: utzoo!watmath!clyde!burl!ulysses!allegra!bellcore!decvax!genrad!panda!talcott!harvard!seismo!brl-tgr!tgr!cottrell@nbs-vms.ARPA
From: cottrell@nbs-vms.ARPA
Newsgroups: net.lang.c
Subject: asm vs hll
Message-ID: <7827@brl-tgr.ARPA>
Date: Tue, 29-Jan-85 17:24:19 EST
Article-I.D.: brl-tgr.7827
Posted: Tue Jan 29 17:24:19 1985
Date-Received: Sat, 2-Feb-85 13:36:56 EST
Sender: news@brl-tgr.ARPA
Organization: Ballistic Research Lab
Lines: 13

That's part of programming. What do you think the macro capability
is there for? Macros are merely inline subroutines. Are you saying
we should not use ban 'JSR' instructions too? The net effect is that
we have to look elsewhere to see what is happening.

> Furthermore, developing macros can make an assembler look more 
> structured and introduce some higher-level concepts, but it normally
> makes the code produced LESS good than hand coding.

If that is true, how can a compiler produce better code than by hand?
High level languages are in a sense complex macros. Anyway, your code
is probably I/O bound. 
*/