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 autolearn=ham autolearn_force=no version=3.4.4 X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 103376,af960bc705aaf51b X-Google-Attributes: gid103376,public X-Google-ArrivalTime: 2002-03-02 16:32:03 PST Path: archiver1.google.com!postnews1.google.com!not-for-mail From: dewar@gnat.com (Robert Dewar) Newsgroups: comp.lang.ada Subject: Re: Complexity of protected objects Date: 2 Mar 2002 16:32:02 -0800 Organization: http://groups.google.com/ Message-ID: <5ee5b646.0203021632.60ce6c7f@posting.google.com> References: <3C7A75F2.30503@worldnet.att.net> NNTP-Posting-Host: 205.232.38.14 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-Trace: posting.google.com 1015115523 25027 127.0.0.1 (3 Mar 2002 00:32:03 GMT) X-Complaints-To: groups-abuse@google.com NNTP-Posting-Date: 3 Mar 2002 00:32:03 GMT Xref: archiver1.google.com comp.lang.ada:20703 Date: 2002-03-03T00:32:03+00:00 List-Id: Jim Rogers wrote in message news:<3C7A75F2.30503@worldnet.att.net>... > Using a protected object to read and write files is a > clear violation of the intention and recommendations for > proctected objects. Protected objects should be > non-blocking. I/O is always potentially blocking. Please prove this *from the RM*. Potentially blocking is a technical term defined in the RM, it does NOT necessarily correspond to the informal notion of some action in the operating system which blocks execution and causes task switching, so whether I/O is forbidden is something you will have to check with the vendor of the compiler you are using, and will depend on what kind of I/O you are doing and how. > You even have some potential blocking issues when storing > an AVL tree. If you dynamically allocate your AVL tree > nodes you have the possibility of running out of memory. > This will either result in a blocking situation, or a > potential loss of data in the AVL tree. Again, I don't see your point, there is nothing at all to stop a protected subprogram from doing dynamic allocation. > > tony gair wrote: > > do things protected objects were not designed for (is > > this an oxymoron?). An oxymoron is the juxtaposition of contrasting terms for literary effect, e.g. "deafening silence". I see nothing literary here, yes, yes, I know, the term has been so badly misused, that some dictionaries by now recognize the degradation of this beautiful word to simply mean contradiction in terms :-)