From: "Matthew Heaney" <matthew_heaney@acm.org>
Subject: Re: Controlled types for resource locking
Date: 1999/09/09
Date: 1999-09-09T00:00:00+00:00 [thread overview]
Message-ID: <37d8245a@news1.prserv.net> (raw)
In-Reply-To: rtfpr6pv1iv73@corp.supernews.com
In article <rtfpr6pv1iv73@corp.supernews.com> , "Pat Rogers"
<progers@NOclasswideSPAM.com> 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
next prev parent reply other threads:[~1999-09-09 0:00 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-09-08 0:00 Controlled types for resource locking Steve Folly
1999-09-08 0:00 ` Matthew Heaney
1999-09-08 0:00 ` tmoran
1999-09-09 0:00 ` Ted Dennison
1999-09-09 0:00 ` Tucker Taft
1999-09-09 0:00 ` Pat Rogers
1999-09-09 0:00 ` Matthew Heaney
1999-09-09 0:00 ` Pat Rogers
1999-09-09 0:00 ` Matthew Heaney [this message]
1999-09-09 0:00 ` Pat Rogers
1999-09-08 0:00 ` David C. Hoos, Sr.
replies disabled
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox