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,1ea92c0e5255811d X-Google-Attributes: gid103376,public X-Google-ArrivalTime: 2003-03-02 01:06:44 PST Path: archiver1.google.com!postnews1.google.com!not-for-mail From: nma124@hotmail.com (steve_H) Newsgroups: comp.lang.ada Subject: Re: Container libraries Date: 2 Mar 2003 01:06:44 -0800 Organization: http://groups.google.com/ Message-ID: <8db3d6c8.0303020106.157c6aa8@posting.google.com> References: <5d6fdb61.0302250317.c49d71a@posting.google.com> <1046214593.420402@master.nyc.kbcfp.com> NNTP-Posting-Host: 64.105.35.110 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-Trace: posting.google.com 1046596004 14362 127.0.0.1 (2 Mar 2003 09:06:44 GMT) X-Complaints-To: groups-abuse@google.com NNTP-Posting-Date: 2 Mar 2003 09:06:44 GMT Xref: archiver1.google.com comp.lang.ada:34789 Date: 2003-03-02T09:06:44+00:00 List-Id: Hyman Rosen wrote in message > People usually want the wrong sort. If someone needs to access > a container simultaneously from multiple tasks, then they should > privide the synchronization, not the container. But this way you will have duplication of effort. Each client/application who wants to use the container needs to add code to provide the synch. outside the container. What one can do is provide 2 versions of the container, one that is synch. and one that is not. If the client knows there will be one task only who will access the container, then use the non-synch. version (which is assumed to be a little faster), else use the other.