Re: Observer Design Pattern
- From: Joe Van Dyk <joe.vandyk@xxxxxxxxxx>
- Date: Wed, 31 May 2006 15:52:51 GMT
Robert Martin wrote:
On 2006-05-31 06:00:00 -0500, "Krivenok Dmitry" <dima@xxxxxxxxxxxxxxxxxx> said:
Hello All!
I am trying to implement my own Design Patterns Library.
If you are talking about a code library (as opposed to a library of documents) then I'd like to discourage you. Design Patterns are not the kind of thing that you can turn into a reusable coding library.
Observer is one of the exceptions to this rule; but it's only a partial exception for the reasons that you have already pointed out in your post.
<snip>
# Ruby
require 'singleton'
class Logger
include Singleton
end
Logger is now a singleton class. Is that one of the exceptions?
Joe
.
- References:
- Observer Design Pattern
- From: Krivenok Dmitry
- Re: Observer Design Pattern
- From: Robert Martin
- Observer Design Pattern
- Prev by Date: Re: Observer Design Pattern
- Next by Date: Re: The wisdom of the object mentors (Was: Searching OO Associations with RDBMS Persistence Models)
- Previous by thread: Re: Observer Design Pattern
- Next by thread: Re: Observer Design Pattern
- Index(es):
Relevant Pages
|