Subject: | |
From: | |
Reply To: | |
Date: | Fri, 7 Nov 1997 07:59:58 -0500 |
Content-Type: | text/plain |
Parts/Attachments: |
|
|
The same situation exists, in Transact, when you use INCLUDEs like they should
be used. Also, if you use some of the other features, like list(auto)... then
you either need to look at dictionary or a compiled version of the code. These
little 'perks' to a language turn out to be a pain when debugging someone else's
code. I think that some of these little 'pains' exist in every language. Like
someone else has already said, you need to pick the tools that suit your needs.
For us, that is Transact, Cognos, and others. For the QWEBS folks, that is
COBOL. etc.
Kevin Newman
______________________________ Reply Separator _________________________________
Subject: Re: Transact Programs
Author: CECILE CHI <[log in to unmask]> at trcinternet
Date: 11/6/97 6:55 PM
But in order to see everything in a program you need to look at several
COPYLIB members, or else generate a compile listing.
Cobol code may be faster to write using copylibs, but maintenance is
slowed down considerably.
I am rewriting some Cobol programs in Transact to make them easier to
read and understand, and particularly to make them easier to maintain.
Cecile Chi
|
|
|