Path: utzoo!utgpu!jarvis.csri.toronto.edu!rutgers!tut.cis.ohio-state.edu!ucbvax!MAINE.BITNET!MICHAEL
From: MICHAEL@MAINE.BITNET (Michael Johnson)
Newsgroups: comp.lang.asm370
Subject: Re: Opsyn
Message-ID: <8906152257.AA05890@jade.berkeley.edu>
Date: 15 Jun 89 22:46:03 GMT
Sender: daemon@ucbvax.BERKELEY.EDU
Reply-To: IBM 370 Assembly Programming Discussion List <ASM370%UCF1VM.bitnet@jade.berkeley.edu>
Distribution: inet
Organization: The Internet
Lines: 14

There is one very good reason that I can think of NOT to use the OPSYN
directive in the way that you, Cem, suggest. This is the simple fact that by
so doing you are probably going to make it immensely difficult for anyone to
later understand and successfully enhance your code, should that ever be
necessary.

One of the cardinal rules of good programming is that you should not use
obscure tricks if you don't have to and if you do have to, you should explain
as fully as you can what you are doing. I dare say renaming the opcodes of
the 370 instruction set counts as an unnecessary trick.

Michael Johnson                           "We are the Priests of the Temples
University of Maine System                 of Syrinx. Our great computers fill
Computing and Data Processing Services     the hallowed halls." - Neil Peart