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=0.6 required=5.0 tests=BAYES_00,TO_NO_BRKTS_FROM_MSSP autolearn=no autolearn_force=no version=3.4.4 X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 103376,7ee10ec601726fbf X-Google-Attributes: gid103376,public X-Google-ArrivalTime: 2001-11-01 07:38:10 PST Path: archiver1.google.com!news1.google.com!newsfeed.stanford.edu!news-spur1.maxwell.syr.edu!news.maxwell.syr.edu!out.nntp.be!propagator-SanJose!in.nntp.be!newsranger.com!www.newsranger.com!not-for-mail Newsgroups: comp.lang.ada From: Ted Dennison References: <3BC5D730.DA950CC7@boeing.com> <9q4pa7$1ad$1@nh.pace.co.uk> <3BC6ACC8.23EF21BC@free.fr> <3BC71F54.1FFE78FA@boeing.com> <1KGx7.26476$ev2.35117@www.newsranger.com> <3BC7AD82.2A0CCCD4@acm.org> <9qhiqr$af0$1@nh.pace.co.uk> <1nDC7.180$6S7.92255364@newssvr11.news.prodigy.com> <9rjsak$bp3$1@nh.pace.co.uk> <9rmhb9$o1b$1@nh.pace.co.uk> <3BDEF0FE.B55FED9E@san.rr.com> <9rmuqi$es$1@nh.pace.co.uk> <3BDF1F13.4B99361C@san.rr.com> <9rnbtv$5i4$1@nh.pace.co.uk> <3BE03E54.57E0E6C8@san.rr.com> Subject: Re: why not Message-ID: X-Abuse-Info: When contacting newsranger.com regarding abuse please X-Abuse-Info: forward the entire news article including headers or X-Abuse-Info: else we will not be able to process your request X-Complaints-To: abuse@newsranger.com NNTP-Posting-Date: Thu, 01 Nov 2001 10:37:29 EST Organization: http://www.newsranger.com Date: Thu, 01 Nov 2001 15:37:29 GMT Xref: archiver1.google.com comp.lang.ada:15540 Date: 2001-11-01T15:37:29+00:00 List-Id: In article , Matthew Heaney says... > >We certainly do NOT agree that data structures should be "task safe." If a >user needs a data structure to work in the presence of multiple threads, >then he needs to build those semantics himself using other primitives >provided by the language. This is completely consistent with how Text_IO >and Numerics.Discrete_Random (for example) are defined. I'm not particularly happy that Text_IO works that way (its a tremendous source of errors), but I think I have to agree. It'd be nice to have task safe versions, but given the state of the rest of the standard Ada library, it would probably be more consistent *not* to have them. However, an instantiation of the facility should be task safe when *different* container objects are being used (no globals). > >> No question. But then it's harder to precisely specify what the behavior >> is without saying "it behaves like this implementation." > >You need to specify time and space semantics for any abstraction. This is a >solved problem. > >> > Since apparently C++ has succeeded in including a similar library in its >> > standard, I wouldn't think the task is either impossible or totally >> > undesirable. I'd just favor a more gradual approach. >> >> But have they succeeded? It took years before any of the STL >> implementations were compatible and correct, IIRC. > >FUD. Of course they succeeded. C++ is vastly simpler to use now that the >STL is part of the standard. > > > > --- T.E.D. homepage - http://www.telepath.com/dennison/Ted/TED.html No trees were killed in the sending of this message. However a large number of electrons were terribly inconvenienced.