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,28c043d47104f5d9 X-Google-Attributes: gid103376,public From: "Matthew Heaney" Subject: Re: Controlled types for resource locking Date: 1999/09/09 Message-ID: <37d8245a@news1.prserv.net>#1/1 X-Deja-AN: 523120358 Content-transfer-encoding: 7bit References: <936824686.950.0.nnrp-07.c2de848f@news.demon.co.uk> <37d7cee7@news1.prserv.net> Content-Type: text/plain; charset="US-ASCII" X-Complaints-To: abuse@prserv.net X-Trace: 9 Sep 1999 21:19:22 GMT, 32.101.8.167 Organization: Global Network Services - Remote Access Mail & News Services Mime-version: 1.0 Newsgroups: comp.lang.ada Date: 1999-09-09T00:00:00+00:00 List-Id: In article , "Pat Rogers" wrote: > "Simpler is in the eye of the beholder". :-) I find it simpler to do > it the other way, but not greatly so. Perhaps I should have said "more flexible." My issue with your approach is that the generic only works for types in that one class (of the imported type). The other way, the generic works for *any* class, and decouples the abstractions. >> I'll be discussing this technique in my Design Patterns tutorial at this >> year's SIGAda conference. > > > When is the book coming out? Don't know yet. I have a couple of book ideas, but I've been busy getting the tutorial slides done for Dave Cook. That's done, so now I can finally start writing... (And I haven't forgotten my promise to you to write some design pattern articles for Ada Letters...) Matt