Re: Reusability



On Sun, 1 Jun 2008 00:31:37 -0700 (PDT), amir <ahsharif@xxxxxxxxx> wrote:

I am looking for reusability strategies, methods and tricks in the
COBOL language and found:
1- Common Reusability:
a. using Copy-Book files and COPY ... REPLACING ... BY ... statement

You should never copy procedure division code. Instead, make it a callable program.

REPLACING is not very useful for data division code. If you need two copies of the same
structure, use OCCURS or qualification.

2- Data Reusability:
a. TYPEDEF is available but not recommended for main-frame development

It is not available in Enterprise Cobol V4. The same can be accomplished with COPY.

3- Code Reusability:
a. subprogram (static or dynamic link):

Dynamic is the norm. Static has been obsolete so long that Micro Focus is dropping
support.

b. section and paragraph

c. Nested programs.

d. Object oriented.

I think all new technology and thought's root is in the before
problems and solved by ancestors and in the new languages and
technologies there is not anything but encapsulated concepts of
before.

Innovators hate that kind of talk. They think their ideas are new.

.