|
Your proc example doesn't need the P after the STON
in line 3. The reasons you have the STON, H< and P(x) on lines 7,8,9 is
twofold. The first reason is that in a typical GET-LIST/LIST pairing, your list
statement could exceed the maximum size of the Secondary Output buffer (STON
without the H< and P). That required Secondary Output buffer extensions of
H<< which needed to be properly placed and when changes were made, you had
to recalculate where they belonged.
Using the STON, H<, P then the HLIST put the
entire LIST statement into the Primary Output buffer which is seemingly
limitless. Like a paragraph, you were executing 2 consecutive
statements.
The downside is that if the preceeding SELECT
doesn't yield any items or the GET-LIST comes up empty, the HLIST will process
your report against the entire file. Thus the IF E=401 concept was introduced to
validate the active list.
That psycho couldn't possibly have programmed that
on purpose. I've seen some excessive use of STOFF/STON pairs, ie STOFF after a P
when it comes automatically. (Like RI then S1. Duh, RI implies S1). The fact
that the psycho alternated their two sentence's words in consecutive statements
was either to hide some code or fool around.
my 1 cent
|
-- u2-users mailing list [EMAIL PROTECTED] http://www.oliver.com/mailman/listinfo/u2-users
