Path: utzoo!attcan!uunet!husc6!mailrus!tut.cis.ohio-state.edu!ucbvax!UIAMVS.BITNET!AWCTTYPA From: AWCTTYPA@UIAMVS.BITNET ("David A. Lyons") Newsgroups: comp.sys.apple Subject: following programming guidelins Message-ID: <8903121951.aa07292@SMOKE.BRL.MIL> Date: 13 Mar 89 00:45:00 GMT Sender: daemon@ucbvax.BERKELEY.EDU Organization: The Internet Lines: 37 >Date: Sat, 11 Mar 89 20:00:39 CST >From: Joey Schober >Subject: GS/OS >Well, a lot of programmers don't follow the guidelines out of >ignorance; a lot of 'em -- particularly authors of Public >Domain/ShareWare applications and DA's -- don't really have the time >or the interest to follow all the rules perfectly, and (a similar >thing) many goals in programming can be accomplished much quicker, >easier, faster, etc. using illegal entry points or whatever. Is this >good for functionality? Sometimes. But is it good for future >compatibility? Nope, unfortunately. Ugh. Lack of _time_ is no excuse at all. Programmers who don't take the time to do things in a correct way just waste the time of their _users_. Don't knock PD & Shareware stuff across the board: sure, there is _some_ low-quality stuff, and there's some high-quality stuff. My stuff follows rules when they exist. Things like Nifty List necessarily assume undocumented things like the structure of a master pointer record. If they change, I'll update Nifty List appropriately. Taking silly shortcuts & other shortsightedness is not only bad for _future_ compatibility: it's also bad for _present_ compatibility with other applications and utilities. BUY THE ADDISON-WESLEY BOOKS! GET THE TECHNOTES! READ THEM! It's usually almost as easy to do things right as to do them wrong. > Joseph F. Schober, Sysop, StarPort BBS [703/931-0947 - 3/12/2400] --David A. Lyons bitnet: awcttypa@uiamvs DAL Systems CompuServe: 72177,3233 P.O. Box 287 GEnie mail: D.LYONS2 North Liberty, IA 52317 AppleLinkPE: Dave Lyons