Newsgroups: comp.windows.x
Path: utzoo!utgpu!news-server.csri.toronto.edu!mailrus!sharkey!msuinfo!news
From: harperb@frith.msu.edu (Brett Harper)
Subject: Object oriented X toolkits
Message-ID: <1990Aug22.164024.12536@msuinfo.cl.msu.edu>
Sender: news@msuinfo.cl.msu.edu
Organization: Michigan State University, College of Engineering
Distribution: usa
Date: Wed, 22 Aug 90 16:40:24 GMT

I have just completed an Object Oriented toolkit for creating X applications.
It all works pretty good and is easy to use, but the size of the executables
that it generates! Let me tell you.  They 'is huge!  A simple program that
is 97 lines long that loads a bitmap and displays it compiles to ~900k

Could somebody tell me if other object oriented X toolkits produce code
that is so obese?  Is there anything to do about it.  Since the code will
be run on a sun4 with at least os 4.0.3 using shared libraries will this be
as big of a problem?  i.e. will two applications use the same library space?
Or will both executable images be loaded in their entirety?

How about InterViews, what is a typical executable size for it?

Thanks, 
 Brett Harper
Case Center for CAEM
Michigan State University

harperb@frith.egr.msu.edu