Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!husc6!bbn!oberon!cit-vax!tybalt.caltech.edu!wetter
From: wetter@tybalt.caltech.edu (Pierce T. Wetter)
Newsgroups: comp.sys.mac
Subject: Re: code optimizers
Message-ID: <4074@cit-vax.Caltech.Edu>
Date: Sat, 26-Sep-87 04:55:48 EDT
Article-I.D.: cit-vax.4074
Posted: Sat Sep 26 04:55:48 1987
Date-Received: Sun, 27-Sep-87 09:50:05 EDT
References: <3924@sdcsvax.UCSD.EDU> <174400056@uxc.cso.uiuc.edu>
Sender: news@cit-vax.Caltech.Edu
Reply-To: wetter@tybalt.caltech.edu.UUCP (Pierce T. Wetter)
Organization: California Institute of Technology
Lines: 31

In article <174400056@uxc.cso.uiuc.edu> dorner@uxc.cso.uiuc.edu writes:
>
>>>Is there a significant interest market for an external optimizer for
>>>the Macintosh/Macintosh II?
>>
>>The best way to do it is to write an optimizer that works directly
>>on code resources in compiled Macintosh applications.  That way,
>>you could take any standard Mac application, and optimize it.
>
>While this sounds good on the surface, I'd have to have a lot of faith
>in an optimizer to do this, because the resultant application would have
>had NO TESTING.  I'd much rather the optimization were done by the
>developers, so that the optimized code would be tested (except for 
>Microsoft, since they don't seem to do any testing :-)).

  On the other hand, it would be pretty hard to screw up things like
mapping two move.w to one move.L. Or perhaps a "smart" segementer. Besides
your faith/lack of   will be determined by your experience. Also in general
copy protected code won't work if it checks to see if it has been modified.

  I think its a good idea but I don't know if I would pay for it.
  Pierce Wetter

The shortest distance between two points is under construction.
		-- Noelie Altito

--------------------------------------------

wetter@tybalt.caltech.edu

--------------------------------------------