Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!usc!ucsd!ucbvax!ECHO.CANBERRA.EDU.AU!eyal
From: eyal@ECHO.CANBERRA.EDU.AU (Eyal Lebedinsky)
Newsgroups: comp.lang.asm370
Subject: Re: Long Programs ( > 4096 bytes)
Message-ID: <9011060531.AA14212@ucbvax.Berkeley.EDU>
Date: 6 Nov 90 05:30:20 GMT
Sender: daemon@ucbvax.BERKELEY.EDU
Reply-To: IBM 370 Assembly Programming Discussion List
              <ASM370@OHSTVMA.BITNET>
Distribution: inet
Organization: The Internet
Lines: 21

In comp.lang.asm370 you write:

>Okay, simple question for those of you who do this sort of thing all the time:

>I am writing a program that has gotten a little long...long enough to lose
>touch with the variables and literals.  I have used the multiple base-registers
>to offset this problem some, but it is still getting at me.  One reason is
>that I manipulate a matrix that is 4k long.  Can anyone make the concept of
>Control Sections and the method of dividing up a task so that each section
>can reference the variables it needs in a common block make sense to me?
To start with, move the BIG data areas to AFTER thr LTORG, then address
those blicks using A(@#$@$#). No need to break the program into multiple
CSECTS. If the code itself is too large then if makes sense to break the
programs into logical parts, each with its own base register (you say
USING at the start of a part, then DROP at the end, and make sure the
base is correct before each USING). Again, no need for multiple CSECTS in
this case.
>AIIIGH!  I hate being born in the age of Pascal and C....I happen to like
>370 ASM....
Nothing wrong with that, every language has a place and asm will still be
with us when most other langs fade away.