Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!samsung!zaphod.mps.ohio-state.edu!sdd.hp.com!elroy.jpl.nasa.gov!aero!aerospace.aero.org!slewis
From: slewis@aerospace.aero.org
Newsgroups: comp.sys.mac.programmer
Subject: Help needed reducing Think C Jump Table Size
Message-ID: <87757@aerospace.AERO.ORG>
Date: 5 Oct 90 19:55:19 GMT
Sender: news@aerospace.aero.org
Reply-To: slewis@aerospace.aero.org ()
Organization: The Aerospace Corporation, El Segundo, CA
Lines: 11


   Help I am developing a THINK_C project with about 120 classes
and 130 files and am running out of Jump Table space. What can I 
do to radically cut my jump table use. Not all classs are used by the
current application but it is difficult to decide which are used.
   If I move some routines to libraries will that eliminate jump
table entries for unreferenced objects. Going through and declaring 
everything that can be static static is a huge job. Do any others have
this problem??
    Symantec- I may have to abandon think C over this issue. Any plans
to up the jump table size??