From mboxrd@z Thu Jan  1 00:00:00 1970
X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me
X-Spam-Level: ***
X-Spam-Status: No, score=3.4 required=5.0 tests=BAYES_50,INVALID_DATE,
	MSGID_SHORT,REPLYTO_WITHOUT_TO_CC autolearn=no autolearn_force=no
	version=3.4.4
Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!cs.utexas.edu!rutgers!mcnc!rti!stdc01!walsh
From: walsh@stdc01.UUCP (Mike Walsh)
Newsgroups: comp.lang.ada
Subject: Re: Use of "is separate" and compilatio
Message-ID: <590@stdc01.UUCP>
Date: 6 Dec 89 12:54:59 GMT
References: <20600021@inmet> <3076@cbnewsl.ATT.COM> <60@array.UUCP> <1501@dinl.mmc.UUCP>
Reply-To: walsh@stdc01.UUCP (Mike Walsh)
Organization: Star Technologies, Graphicon Products Division (RTP, N.C)
List-Id: <comp.lang.ada>

In article <1501@dinl.mmc.UUCP> schwartz@dinl.UUCP (Michael Schwartz) writes:
>
>> why do we need 'is separate'
>
'is seperate' is useful for extracting certain procedures from a package.
I once wrote a package that had a classified algorithm in it.  By making the
one procedure separate, I could print out the file, and not have to worry
about having a classified document laying around.  Just an example ...


Mike Walsh
Star Technologies - Graphicon Products Division
Research Triangle Park, NC

walsh@stdc01    {...uunet!mcnc!rti!stdc01!walsh}