Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!cs.utexas.edu!usc!brutus.cs.uiuc.edu!zaphod.mps.ohio-state.edu!sunybcs!sbcs!vallon
From: vallon@sbcs.sunysb.edu (Justin Vallon)
Newsgroups: comp.sys.mac.programmer
Subject: Re: Communications Toolbox questions
Message-ID: <4179@sbcs.sunysb.edu>
Date: 6 Dec 89 22:40:04 GMT
References: <9125@hoptoad.uucp> <36869@apple.Apple.COM> <9194@hoptoad.uucp> <TIME.89Dec5172829@oxtrap.oxtrap.UUCP>
Sender: news@sbcs.sunysb.edu
Reply-To: vallon@sblw.UUCP (Justin Vallon)
Organization: State University of New York at Stony Brook
Lines: 24

In article <TIME.89Dec5172829@oxtrap.oxtrap.UUCP> time@oxtrap.UUCP writes:
>Tim Maroney writes:
>>[Make a 'Comm' type which is a Comm INIT, loaded by the toolbox INIT]
>
>Also, is it really necessary to even make the 'Comm' inits? Couldn't
>INIT 31 be made smart enough to look for CTB first? Or, couldn't the
>INIT 31 be programmed to look for a resource in an INIT called 'Comm'
>which indicates that this INIT uses the CTB, and therefore must be
>delayed until CTB is loaded (or possibly not loaded in case of no CTB).
>ANYTHING, but what is done now would be better.
>
>tim

Two points:

1)  That would mean that you would have to modify all current INIT 31's
    before running the Comm Toolbox.

2)  Why not use the 'Comm' file-type.  It is easy, prevents pointless
    execution of Comm INITs without Toolbox installed, and doesn't have
    to change anything that currently exists.

-Justin
vallon@sbcs.sunysb.edu