Path: utzoo!attcan!uunet!mcvax!sunic!kth!draken!d88-jwa From: d88-jwa@nada.kth.se (All this was brought to you by h+@nada.kth.se Replys via email welcome!) Newsgroups: comp.sys.mac Subject: Re: Real Multifinder Message-ID: <1428@draken.nada.kth.se> Date: 17 Aug 89 22:42:25 GMT References: <46100321@uxe.cso.uiuc.edu> <1989Aug15.001507.14552@sj.ate.slb.com> <24626@iuvax.cs.indiana.edu> <3576@internal.Apple.COM> <1989Aug16.175351.24310@sj.ate.slb.com> <7420@microsoft.UUCP> Reply-To: d88-jwa@nada.kth.se (Jon W{tte) Organization: Royal Institute of Technology, Stockholm, Sweden Lines: 30 In article <7420@microsoft.UUCP> t-stevep@microsoft.UUCP (Steve Pool) writes: >I really think it's time for the Mac programming model to be updated. >That's probably unreasonable, considering the amount of code that would >undoubtedly cease functioning, but it would sure make me happy! Of course not! Already working code has no reason to break even if we change the future development system. You'll just have a skeleton ready, where you put in your (pointers to) functions. I thought that MacApp already did this. I could be wrong, I haven't used it. Anyway, it's a piece of cake to write a "universal" dispatcher module and compile it as a library to link with your other code. Then you could either a) have special names for your target routines (i.e. doMenu) b) use a struct that's set up in the initialization and that contains pointers to all of your routines. (Better still, handles to them. Be sure to lock the segments that your routines are in, since things will be weird otherwise !) Since Apple now wants us to use OOP, thing should get still easier. MicroSoft may try to do things right, but in my opinion, they haven't really gotten that far yet. Have a nice day! h+@nada.kth.se -- This is your fortune from h+@nada.kth.se: Xerox does it again and again and again and...