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=-1.9 required=5.0 tests=BAYES_00,FREEMAIL_FROM autolearn=ham autolearn_force=no version=3.4.4 X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 103376,78546269947cb927 X-Google-Attributes: gid103376,public X-Google-ArrivalTime: 2004-03-29 14:19:03 PST Path: archiver1.google.com!news1.google.com!news.glorb.com!newsfeed1.uni2.dk!news.get2net.dk.POSTED!53ab2750!not-for-mail Newsgroups: comp.lang.ada Subject: Re: Combining entry_call, accept_statment and terminate_statment References: <106h7clrs4iio8c@corp.supernews.com> From: Mark Lorenzen Message-ID: User-Agent: Gnus/5.1002 (Gnus v5.10.2) Emacs/21.3 (gnu/linux) Cancel-Lock: sha1:sGI/Br4NwjIXico55IvtVpSHIQc= MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 30 Mar 2004 01:19:34 +0200 NNTP-Posting-Host: 82.180.17.195 X-Complaints-To: abuse@colt-telecom.dk X-Trace: news.get2net.dk 1080598740 82.180.17.195 (Tue, 30 Mar 2004 00:19:00 CEST) NNTP-Posting-Date: Tue, 30 Mar 2004 00:19:00 CEST Organization: Colt Telecom Kunde Xref: archiver1.google.com comp.lang.ada:6660 Date: 2004-03-30T01:19:34+02:00 List-Id: "Randy Brukardt" writes: [cut] > > But I'd say that you probably have a design problem if you have a task that > is both calling and accepting at the same time. That's pretty weird (unless > the accepts are purely for task control, as above). It's preferable that > each task be either a server (accepting entries) or a client (calling > entries), but not both. Analysis is complicated if you have both. > > Randy. To me, this seems to be a severe design limitation. Isn't it normal to have a task acting as a filter, i.e. reading data from a PO, manipulating the data and the writing the manipulated data to a PO? This could f.x. be a task implementing a (de)multiplexer. - Mark Lorenzen