Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Path: utzoo!mnetor!seismo!gatech!mit-eddie!genrad!decvax!ucbvax!ANDREW.CMU.EDU!rs4u# From: rs4u#@ANDREW.CMU.EDU (Richard Siegel) Newsgroups: comp.sys.mac Subject: Change in "_Launch" interface... Message-ID: Date: Fri, 1-May-87 07:38:12 EDT Article-I.D.: andrew.MUa8YYy00UhTQM00cm Posted: Fri May 1 07:38:12 1987 Date-Received: Sat, 2-May-87 16:53:10 EDT Sender: daemon@ucbvax.BERKELEY.EDU Lines: 46 Some questions: 1) Why the change? It seems to me that there's a large number of programs that have the "Transfer" feature (as it's usually called), that will suddenly stop working. 2) For Old Mac and Mac Plus owners (Old Mac = 64K ROM), does this change come with System 4.x? Or is it simple a change in the ROM for the SE and Mac II, so the "Transfer" feature will only crash on the new machines? 3) *Flame On* Why is Apple doing this? I personally would simply add another trap (_SubLaunch or somehting) to the 256K ROMs, or make the existing _Launch trap smart enough to know when it's being called with the old protocol, and adjust accordingly. As I said, a lot of existing applications will suddenly stop working, and there are going to be a lot of pissed-off users (not to mention developers!) out there. I may not be looking at things realistically, but... *Flame Off* 4) By the way, will this interface change be backward compatible? Suppose I fix the application to use the new interface. What if someone runs it on an older System? Does it break then? Or will some way be provided for the application to know which interface to use? "I would advise people to wait the week or two for the technote before implementing a lot of Launch code that will have to be changed. Great. 8-) --Rich Richard M. Siegel Materials Characterization Instrumentation Section Mail Stop 231 NASA/Langley Research Center Hampton, Virginia 23665 (804) 865-3036 Arpanet: rs4u@andrew.cmu.edu Uucp: {your fave gateway}!seismo!andrew.cmu.edu!rs4u Disclaimer? I don't even KNOW 'er!