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.3 required=5.0 tests=BAYES_00,INVALID_MSGID autolearn=no autolearn_force=no version=3.4.4 X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 103376,71daebeb6145ebb6 X-Google-Attributes: gid103376,public From: dennison@telepath.com Subject: Re: Stream venting (long) Date: 1998/12/30 Message-ID: <76doir$1ek$1@nnrp1.dejanews.com>#1/1 X-Deja-AN: 427149053 References: <768sng$6r9$1@nnrp1.dejanews.com> <769g3r$moq$1@nnrp1.dejanews.com> <76aor7$l4q$1@nnrp1.dejanews.com> <76baib$4ne$1@nnrp1.dejanews.com> <76de7d$opb$1@nnrp1.dejanews.com> <76dh6m$r63$1@nnrp1.dejanews.com> X-Http-Proxy: 1.0 x10.dejanews.com:80 (Squid/1.1.22) for client 204.48.27.130 Organization: Deja News - The Leader in Internet Discussion X-Article-Creation-Date: Wed Dec 30 17:40:43 1998 GMT Newsgroups: comp.lang.ada X-Http-User-Agent: Mozilla/4.5 [en] (WinNT; I) Date: 1998-12-30T00:00:00+00:00 List-Id: In article <76dh6m$r63$1@nnrp1.dejanews.com>, robert_dewar@my-dejanews.com wrote: > In article <76de7d$opb$1@nnrp1.dejanews.com>, > that way. The details of the locking should be buried in > the stream attribute routines that you write. If you want > the locking mechanism to be general, you could even make > an extended stream type that had the necessary lock field, > but most likely it would be perfectly convenient to just > use a single global lock. > Ahh. I see we have different ideas about what "client" means. To me the "client" of my stream package *is* the writer of the stream attribute routines. I have no clue how to write those routines for them, as I have no prior knowledge of what they want to write (or access into their packages). In fact, they may want to use the default routines in many cases. So we're stuck with the crappy interface. -- T.E.D. -----------== Posted via Deja News, The Discussion Network ==---------- http://www.dejanews.com/ Search, Read, Discuss, or Start Your Own