From mboxrd@z Thu Jan  1 00:00:00 1970
X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me
X-Spam-Level: 
X-Spam-Status: No, score=0.1 required=5.0 tests=BAYES_05,INVALID_MSGID
	autolearn=no autolearn_force=no version=3.4.4
X-Google-Language: ENGLISH,ASCII-7-bit
X-Google-Thread: 103376,658cbf6222fa4bf5,start
X-Google-Attributes: gid103376,public
From: tmoran@bix.com (Tom Moran)
Subject: OO and large packages
Date: 1998/04/23
Message-ID: <353f7983.1926480@SantaClara01.news.InterNex.Net>#1/1
X-Deja-AN: 347036824
Organization: InterNex Information Services 1-800-595-3333
Newsgroups: comp.lang.ada
Date: 1998-04-23T00:00:00+00:00
List-Id: <comp.lang.ada>


Is there a good methodology to break up a complex object into multiple
smaller packages?
  In a windowing system I have a "window" object with a great many
functions for both input and output, some of which are rather complex.
One possible split is 
  type output_window is new basic_window ...
and a package providing just the output functions, then another
package with
  type input_window is new output_window ...
overiding the input functions of basic window (which weren't even
mentioned in input_window).  That produces two, smaller, package, but
output_window is secretly passing all the input functions from
basic_window on to input_window, which seems a really poor idea.
  The only other obvious breakup is to include everything in one large

  type io_window is new basic_window ...
but move the guts of the larger functions off to separate packages in
a traditional bottom-up way, with no special conceptual structure.
  Suggestions?