Re: "Shared" procedure division code
- From: "Caederus" <davidburnham@xxxxxxxxx>
- Date: 26 Jul 2005 09:17:28 -0700
> I neither recommend this approach nor (personally) know of any reason to use it
> in today's computing environment, but did think it was worth mentioning (both
> for the "use of duplicated code" and the solution to "maintenance of such code")
Maintenance of the code is the big reason to use such code.
If you have a routine that works and is used by a number of different
programs, putting it in a copybook is the quickest and easiest way to
stream line the maintenance. However If it starts getting to big there
is the question of making it it's own sub program.
.
- References:
- "Shared" procedure division code
- From: William M. Klein
- "Shared" procedure division code
- Prev by Date: Re: "Shared" procedure division code
- Next by Date: Re: sequential file formats
- Previous by thread: Re: "Shared" procedure division code
- Next by thread: Re: "Shared" procedure division code
- Index(es):
Relevant Pages
|