Re: Date manipulation
From: Howard Brazee (howard_at_brazee.net)
Date: 12/29/03
- Previous message: Howard Brazee: "Re: COBOL Standards Issue"
- In reply to: Judson McClendon: "Re: Date manipulation"
- Next in thread: Judson McClendon: "Re: Date manipulation"
- Reply: Judson McClendon: "Re: Date manipulation"
- Reply: Richard: "Re: Date manipulation"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Mon, 29 Dec 2003 19:20:00 GMT
On 29-Dec-2003, "Judson McClendon" <judmc@sunvaley0.com> wrote:
> > Six invokes for a command used once in a program is nothing. Decisions
> > such as
> > this should be made solely on maintenance efficiency, not run-time
> > efficiency.
>
> If that code is in a transaction routine that is called 1000 times a second,
> the overhead isn't 'nothing'. And what about turning over midnight after
> the first call and before the last call? Remember Murphy's Law. :-)
But you will notice that the code said:
DISPLAY 'SIPR702 BEGAN ' FUNCTION CURRENT-DATE (5:2)
'/' FUNCTION CURRENT-DATE (7:2)
'/' FUNCTION CURRENT-DATE (1:4)
' ' FUNCTION CURRENT-DATE (09:2) hour
':' FUNCTION CURRENT-DATE (11:2)
':' FUNCTION CURRENT-DATE (13:2).
Saying when a program starts doesn't happen 1000 times a second.
I was under the impression that this gets converted into one call though.
- Previous message: Howard Brazee: "Re: COBOL Standards Issue"
- In reply to: Judson McClendon: "Re: Date manipulation"
- Next in thread: Judson McClendon: "Re: Date manipulation"
- Reply: Judson McClendon: "Re: Date manipulation"
- Reply: Richard: "Re: Date manipulation"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|
|