Re: CoBOL moved to OO

From: Howard Brazee (howard_at_brazee.net)
Date: 01/08/04 

Date: Thu, 8 Jan 2004 16:19:30 GMT

On 7-Jan-2004, Donald Tees <donald_tees@nospam.sympatico.ca> wrote:

> Consider the traditional Cobol system based on a main menu, with each
> program being a subroutine, and the common setup data being read by the
> menu. Structurally, it normally looks as follows.
>
> Main program
> call read setup stuff
> menu loop
> choose program
> call program using setup-data
> end menu loop
> stop.

On mainframes that I have worked on, the menu programs have been outside of
CoBOL programs. But it seems that menus are pretty much thinking in OO anyway.

Do you have any non-interactive examples where OO commands are useful to people
who don't "think" in OO?

Or maybe I misunderstand - that you are recommending it to replace all called
programs. From reading your post, I think this may be the case - that you
think passed arguments are a pain, and that programmers should learn to use
"invoke" as a way of avoiding passing arguments.