Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!uwm.edu!cs.utexas.edu!samsung!brutus.cs.uiuc.edu!rpi!batcomputer!eacj
From: eacj@batcomputer.tn.cornell.edu (Julian Vrieslander)
Newsgroups: comp.sys.mac.programmer
Subject: Re: THINK C build speed-up
Message-ID: <9231@batcomputer.tn.cornell.edu>
Date: 6 Nov 89 15:28:57 GMT
References: <5804@ucdavis.ucdavis.edu> <32366@ucbvax.BERKELEY.EDU>
Reply-To: eacj@tcgould.tn.cornell.edu (Julian Vrieslander)
Organization: Cornell Theory Center, Cornell University, Ithaca NY
Lines: 18

In article <32366@ucbvax.BERKELEY.EDU> oster@dewey.soe.berkeley.edu.UUCP (David Phillip Oster) writes:
>I would expect an application built from THINK C to be slightly faster
>than running the project, because any GetResource() of code will have to
>search the resource map of the ".rsrc" file, fail to find it there, and
>have to go to the resource map of the ".proj" file to find the resource.
>As an application, it would find it in its own resource file. A little
>faster.  

A couple of my projects actually run a few percent faster as projects
than as applications. These programs do very little accessing of resources,
but are very math-intensive (lotsa FPU calls).

Just another precinct reporting..
-- 
Julian Vrieslander 
Neurobiology & Behavior, W250 Mudd Hall, Cornell University, Ithaca NY 14853    
UUCP: {cmcl2,decvax,rochester,uw-beaver}!cornell!batcomputer!eacj
INTERNET: eacj@tcgould.tn.cornell.edu     BITNET: eacj@CRNLTHRY