Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!usc!snorkelwacker.mit.edu!ira.uka.de!smurf!urlichs From: urlichs@smurf.sub.org (Matthias Urlichs) Newsgroups: comp.sys.mac.programmer Subject: Re: Local/AppleTalk Connectivity in MacApp Message-ID: Date: 5 Jan 91 18:05:31 GMT References: <1991Jan3.221839.21979@athena.cs.uga.edu> <14545@hoptoad.uucp> Organization: University of Karlsruhe, FRG Lines: 23 In comp.sys.mac.programmer, article <14545@hoptoad.uucp>, tim@hoptoad.UUCP (Tim Maroney) writes: < < Incidentally, MacAppers -- please ignore the example programs shipped < by Apple. They are very small and do not scale well. If you adopt the < unit strategy of the example programs, in which everything knows about < the applications and document subclasses and those subclasses know < about everything else, you will not be able to expand beyond a few < source files or do much information hiding or code reusability. < Hmm, perhaps the MacApp sample programs were intended to show specific features of MacApp, and not to be templates for big applications? Relates to this problem, unfortunately, is the fact that the Pascal USES clause is purely textual, not recursive, and can't be specified in the IMPLEMENTATION section (unless you play with {$IFC xyzzy} and {$I xyzzy.stuff.p.include}, which generates other problems). That's where MacApp-compatible languages like Modula-2 come in... -- Matthias Urlichs -- urlichs@smurf.sub.org -- urlichs@smurf.ira.uka.de /(o\ Humboldtstrasse 7 - 7500 Karlsruhe 1 - FRG -- +49+721+621127(0700-2330) \o)/