Path: utzoo!attcan!uunet!portal!cup.portal.com!Michael_mkahl_Kahl From: Michael_mkahl_Kahl@cup.portal.com Newsgroups: comp.sys.mac.programmer Subject: Re: AppleShare-able Compilers Message-ID: <6893@cup.portal.com> Date: 26 Jun 88 17:13:34 GMT References: <4812@husc6.harvard.edu> <382@piring.cwi.nl> Organization: The Portal System (TM) Lines: 19 XPortal-User-Id: 1.1001.4169 >>and furthermore, the compilers save configuration settings in themselves, >>subject to a user command. >Yes. I hate this. Apple has long declared that applications should not >modify themselves to set options etc., but use a "profile" file instead, >and exactly for this reason (shared volumes). It's probably too late >with 3.0 out and everything, but I think that options should be stored >in the project files, especially options that change the syntax of the >language or affect properties of the generated code. 3.0 does indeed store all options on a per-project basis. It also retains the ability to store default options -- these are the options that will be assigned to newly created projects. Default options continue to be stored in the application itself, not in a separate "profile" file. It is all very well that Apple has "declared" that we should be shareable, but the fact is we don't *want* to be shared. We'd prefer that each user purchase a separate copy. -- Michael Kahl, Symantec