Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!wuarchive!gem.mps.ohio-state.edu!swrinde!ucsd!ucbvax!hoptoad!tim
From: tim@hoptoad.uucp (Tim Maroney)
Newsgroups: comp.sys.mac.programmer
Subject: Re: INIT getting it's file name...
Message-ID: <8838@hoptoad.uucp>
Date: 29 Oct 89 22:59:55 GMT
References: <56505@tiger.oxy.edu> <4020@helios.ee.lbl.gov> <5511@umd5.umd.edu> <8831@hoptoad.uucp> <13474@reed.UUCP>
Reply-To: tim@hoptoad.UUCP (Tim Maroney)
Organization: Eclectic Software, San Francisco
Lines: 25

In article <8831@hoptoad.uucp> tim@hoptoad.UUCP (Tim Maroney) writes:
>Three:  I have always felt that the ability to rename INITs is
>overrated.  I mean, who cares if you can or not?  However, few people
>agree with me on this.

In article <13474@reed.UUCP> chaffee@reed.UUCP (Alex Chaffee) writes:
>That's because few people have never had an INIT conflict that could only be
>resolved by (guess what) renaming the INIT files.  Renaming INITs is vital.

Any INIT so brain-damaged that this happens, or any combination of
INITs which interact unpredictably in this way, should be dragged to
the trash can.  I don't understand how people can be so devil-may-care
about their system reliability.  I use very few INITs and for that
reason, when my development software does something strange, I
generally feel confident that it's my code's fault and I don't waste
time messing around with possible INIT problems.  INITs are a necessary
evil and should be treated as such.
-- 
Tim Maroney, Mac Software Consultant, sun!hoptoad!tim, tim@toad.com

"The pride of the peacock is the glory of God.
 The lust of the goat is the bounty of God.
 The wrath of the lion is the wisdom of God.
 The nakedness of woman is the work of God."
    - Blake, "The Marriage of Heaven and Hell"