Re: Laser Printing from MFCOBOL 4.5



"HeyBub" <heybub@xxxxxxxxxxxxxxx> wrote in message
news:s42dnX89HsNrQ0_VnZ2dnUVZ_rmdnZ2d@xxxxxxxxxxxxxxxx
Michael Mattias wrote:
"HeyBub" <heybub@xxxxxxxxxxxxxxx> wrote in message
news:6LmdnZhwvp_r7E_VnZ2dnUVZ_jqdnZ2d@xxxxxxxxxxxxxxxx
As an aside, this illustrates the wonderfulness of putting I/O in a
sub-program. In our case, it was a, maybe, ten-line change to
optionally divert printing to a file instead of LPT1. Re-link of 80
programs and we were good to go.

So near, yet so far....

Wouldn't have had to re-link anything if you had called the I-O module
dynamically.


Well, yeah. But in an old DOS suite, it seemed easier...

I am an ardent supporter of tiered architecture, with separation layers
(interfaces).

There are SO many benefits in doing this which are simply not apparent when
you first do it. After you implement a few systems using this architecture,
and some years go by, you suddenly find benefits which you couldn't envision
crawling out of the woodwork. Swap the data resource to the latest
technology (maybe even a new technology...), but don't change the business
logic...? Easy. Want to move from green screens to GUI? Easy. The list goes
on.

I'm sold.

Pete.
--
"I used to write COBOL...now I can do anything."


.

Relevant Pages

  • Re: Laser Printing from MFCOBOL 4.5
    ... sub-program. ... optionally divert printing to a file instead of LPT1. ... Wouldn't have had to re-link anything if you had called the I-O module ...
    (comp.lang.cobol)
  • Re: Laser Printing from MFCOBOL 4.5
    ... sub-program. ... divert printing to a file instead of LPT1. ... Wouldn't have had to re-link anything if you had called the I-O module ...
    (comp.lang.cobol)