Re: COBOL "non-myth" confirmed - Index and subscripts (MF on Windows)

docdwarf@xxxxxxxxx wrote:
In article <X9-dnYZshvgMLGzbnZ2dnUVZ_remnZ2d@xxxxxxxxxx>,
donald tees <donaldtees@xxxxxxxxxxxxx> wrote:
Howard Brazee wrote:

[snip]

I have a program that looks to see what campus is running that
program. If it is one of the big campuses, it does an area sweep, if
it's one of the small campuses, it walks the set. This was
determined by testing the speeds of the two choices.
Closer to what I mean. Two completely different methodologies, depending on requirements.

This is one of the reasons I've coded

READ INFILE
AT END SET NO-MORE-INPUT TO TRUE
NOT AT END
ADD 1 TO LOOKUP-TBL-ENTRY-NO
IF LOOKUP-TBL-ENTRY-NO > MAX-TBL-ENTRIES-ALLOWED
MOVE 'LOOKUP TABLE EXCEEDS MAX ENTRIES - CALL PROGAMMING'
TO WS-ABEND-REASON
GO TO ABEND-RTN
ELSE
MOVE INREC TO LOOKUP-TBL-ENTRY (LOOKUP-TBL-ENTRY-NO)
END-IF
END-READ

... or reasonable facsimiles thereof. When data volume goes a certain amount beyond program design then it's time to have a coder look at it... if only to say 'Oh, we're not limited to 32K tables any more, let's bump this baby up a few!'.

DD

Probably a good example for two reasons ... it shows a "semi-micro" example that *is* within a program, yet is still an algorithmic difference.

I think most such differences, though, take place well before you get into the middle of a single program. They take place at the design level.

Donald
.