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-Thread: 103376,e44790cdcea9da82 X-Google-Attributes: gid103376,public X-Google-Language: ENGLISH,ASCII-7-bit Newsgroups: comp.lang.ada Subject: Re: Problem with -gnatt References: <41651D37.4030805@mailinator.com> <2skt9qF1ljjdtU1@uni-berlin.de> <4165472D.2030704@mailinator.com> <416573FA.4010003@mailinator.com> <87k6u2mj08.fsf@insalien.org> <4166538E.6090907@mailinator.com> <41702af7$0$91003$39cecf19@news.twtelecom.net> <417377F7.7050506@mailinator.com> <4173f0ed$0$91003$39cecf19@news.twtelecom.net> <417409AB.8040702@mailinator.com> From: Brian May Date: Tue, 19 Oct 2004 12:41:10 +1000 Message-ID: User-Agent: Gnus/5.1006 (Gnus v5.10.6) Emacs/21.3 (gnu/linux) Cancel-Lock: sha1:nxFpWDE1ZK7vk/lDQeH9MRUn4VM= MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii NNTP-Posting-Host: dsl-202-173-153-89.vic.westnet.com.au X-Trace: news.melbourne.pipenetworks.com 1098153656 202.173.153.89 (19 Oct 2004 12:40:56 +1000) X-Complaints-To: abuse@pipenetworks.com X-Abuse-Info: Please forward all headers to enable your complaint to be properly processed. Path: g2news1.google.com!news1.google.com!news.glorb.com!newsfeed-east.nntpserver.com!nntpserver.com!news1.optus.net.au!optus!news.mel.connect.com.au!news-north.connect.com.au!news.alphalink.com.au!news.melbourne.pipenetworks.com!not-for-mail Xref: g2news1.google.com comp.lang.ada:5425 Date: 2004-10-19T12:41:10+10:00 List-Id: >>>>> "Matthew" == Matthew Heaney writes: Matthew> What do you have against semaphores? As long as you Matthew> arrange for the semaphore to get released (which you can I thought the whole idea of protected types is that they were designed to prevent this type of mistake (either forgetting to lock semaphore or forgetting to release it). Also, I have read that implementing a semaphore using a protected type isn't very efficient, as protected types weren't designed for this purpose. Matthew> do using a controlled helper type, as in my example), Matthew> then there's no reason not to use a semaphore. This wont prevent mistakes where you forget to lock the semaphore. -- Brian May