Re: Set numeric value to INDEX was Re: cobol array editing output
From: Judson McClendon (judmc_at_sunvaley0.com)
Date: 12/17/03
- Next message: docdwarf_at_panix.com: "Re: State of WORKING-STORAGE in Statically-Called Subroutines"
- Previous message: Judson McClendon: "Re: In defence of the indefensible. WAS: Re: COBOL array editing output"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Wed, 17 Dec 2003 06:10:54 -0600
"Clark F. Morris, Jr." <cfmtech@istar.ca> wrote:
> >
> > Since range checks have to be performed on the SET that would occur
> > in the called subprogram anyway, and presuming that the implementor
> > has provided a USAGE that corresponds in format to that which would
> > be used for an index, it seems to me unlikely that the SET of an
> > index-name to an index data item would differ *significantly* in
> > performance from the SET of an index-name to a numeric data item. I
> > see maybe a couple of math ops difference. Yes, there is a
> > difference, but I'm not convinced that difference is likely to be
> > significant compared to everything else the called program would be
> > expected to do.
I agree. On architectures I am familiar with, the overhead of calling a
procedure or function is considerably greater than a couple of math ops,
not including any other processing the procedure or function does.
-- Judson McClendon judmc@sunvaley0.com (remove zero) Sun Valley Systems http://sunvaley.com "For God so loved the world that He gave His only begotten Son, that whoever believes in Him should not perish but have everlasting life."
- Next message: docdwarf_at_panix.com: "Re: State of WORKING-STORAGE in Statically-Called Subroutines"
- Previous message: Judson McClendon: "Re: In defence of the indefensible. WAS: Re: COBOL array editing output"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]