Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!cs.utexas.edu!usc!apple!farrier From: farrier@Apple.COM (Cary Farrier) Newsgroups: comp.sys.apple Subject: Re: Problems for a new IIGS user (FST's) Message-ID: <5205@internal.Apple.COM> Date: 15 Nov 89 21:03:03 GMT References: <2634.cortland.info-apple@pro-houston> Organization: Apple Computer Inc, Cupertino, CA Lines: 31 In article <2634.cortland.info-apple@pro-houston> dkl@pro-houston.cts.com (David Karl Leikam) writes: > And if it's the case that they must be SO strictly drawn that little or no >development of that kind is possible, then I must ask, "Why have FST's, or the >capability for them, at all? If they can't be implemented, why waste the disk >space and time to store/access 'em as separate files, rather than embedding >the code into the rest of the O/S???" If you can't use 'em, what good are >they? If you _can_, let us see what use can be made! *Using* an FST is _not_ the same as *writing* an FST! One of the intracacies of creating an FST involves how closely it interacts with the rest of the OS. Sometimes these details change in an OS revision. When this happens, we can update the FSTs, but we can't update a 3d party FST. Do you not drive a car because you can't manufacture it yourself? Do you not buy software because the the author doesn't publish the source code? Just because every individual can't be involved in the creation process doesn't mean that the end product is not useful. Cary Farrier -- +---------------------------------------+---------------------------------+ | Cary Farrier | Internet : farrier@apple.com | | Apple II Systems Software Engineering | UUCP : apple!farrier | | Apple Computer, Inc. | Fax : (408) 974-1704 | | 20525 Mariani Ave. | AppleLink : FARRIER | | Cupertino, CA 95014 | -or- : applelink.apple.com | +---------------------------------------+---------------------------------+ | I don't speak for Apple Computer, our products do that just fine. | +-------------------------------------------------------------------------+