unsubscribe
Non-reentrant programming is /required/ for some platforms -- TPF, ALCS, (and,
I would suspect, CICS?) Many programmers /only/ learn non-reentrant
programming.
I would very much approve of the idea of starting with the simple stuff first:
which in my book would be baseless, non-reentrant
I use a technique in which I create a CSECT with all of my initial values in
it, including any DCBs and associated control blocks. On startup I copy that
CSECT in its entirety to GETMAIN storage with a single MVCL. I then use the
CSECT data definitions to address the DSECT.
Seventeen years ago
On Sat, Sep 17, 2022 at 10:29 AM Ed Jaffe
wrote:
> On 9/17/2022 2:06 AM, Abe Kornelis wrote:
> > Starting with reentrant programming seems a pretty tough call.
>
> Not sure why re-entrant programming should be considered heavy lifting.
> Would not any assembler course teach about USING?
>
For
On Sat, 17 Sept 2022 at 11:29, Ed Jaffe wrote:
[...]
> If I were to teach an HLASM course, I can envisage my very first
> recommended program organization diagram showing both a code and a data
> segment and never once suggesting at any time during the class that code
> and data can be (or ever
I'm with Ed, or even more in the "reentrant direction."
I think reentrant code is hard or "special" only if -- like many of us -- you
have a 20 or 30 year background in thinking non-reentrant code was the normal
way of doing things. No need to teach that.
No one teaches "reentrant C coding" --
On 9/17/2022 2:06 AM, Abe Kornelis wrote:
Starting with reentrant programming seems a pretty tough call.
Not sure why re-entrant programming should be considered heavy lifting.
Would not any assembler course teach about USING?
A typical non-reentrant program has a single code/data segment
Gary, all
Having taught a computer science introductory course on assembler at USF many
years ago, I started with more basic concepts including instruction and data
area addressability, base registers, and common instruction types. At the
time, students had to write a program which read data
Gary,
the z Architecture has a long history, it has built up lots of
complexities that are
difficult to grasp when you start at the most complex end.
>From my experience as an assembler instructor the complexities are best
added and explained layer by layer. I usually explain what the
