Very few monks know about this excelent on-line book for Design Patterns lovers.

-- yuriy

Replies are listed 'Best First'.
Re: Perl Design Patterns Book
by davorg (Chancellor) on Oct 03, 2002 at 16:30 UTC
Re: Perl Design Patterns Book
by VSarkiss (Monsignor) on Oct 03, 2002 at 20:39 UTC

    Sometimes I think the whole Design Patterns thing is getting over-hyped. That's why I found the"Design Patterns" aren't talk from Dominus so refreshing. Read it for an alternative viewpoint.

      I agree that it's an interesting article, but my understanding is that he wasn't saying "design patterns are bad". He was merely saying, "what programmers call 'design patterns' aren't what the original term 'design patterns' referred to". That's why the title is "'Design Patterns' aren't" rather than "'Design Patterns': 99% Bad". :-)

      Wally Hartshorn

Re: Perl Design Patterns Book
by valdez (Monsignor) on Oct 03, 2002 at 19:49 UTC

    From Perl Design Patterns Book:


    Because we don't know how programs will reinvent themselves, we don't know how to design an "Interface" *, what composite types are involved, and what containment and inheritance hierarchies will look like. In the beginning, we seldom know that a program will grow into this at all!

    "Interface" is much more trendy than the ailing "Application Programmer Interface", or "API". Generally speaking, an interface is how you use something. Just like any consumer appliance, modules should be used in very specific ways: do not submerse in water. Do not use while driving. Do not paint over vents. Do not insert fingers. Do not leave on "high" setting unattended. Not only do programs use APIs to talk to the outside world, they use them internally to connect parts.

    Perl's easy going attitude and powerful features shine here. After a program has devised a solution to a logic problem, and after it has proved its continued usefulness, we have a route for improvement.

    Ciao, Valerio

    Update: thank you all for the links, really interesting. It would be nice to see these links listed in tutorials.

    Another quote, but from Dominus's site:

    The "Design Patterns" solution is to turn the programmer into a fancy macro processor


Re: Perl Design Patterns Book
by scrottie (Scribe) on Nov 07, 2002 at 10:52 UTC
    Wow! "Excellent!" I'm truely humbled. For posterity, I should say a few things. First, I agree with MJ Dominus strongly and try to steer clear of suggesting that anyone ever do anything that would require more typing rather than less. Second, I'm in touch with the creator of His site has been around longer and writes for a broader audiance. He suffers from a problem that I don't, though: employement. Third, suffers from a horrid lack of feedback. The few people that wander in always manage to stumble on the the pages that are merely placeholders then wander off as quickly as they came in. This is causing a serious chicken-and-egg problem where I don't want to tell anyone about it because it probably sucks really bad in a way that I can't see, but no one is going to tell me exactly how it sucks so I can improve it unless they see it. Argh! Instead of stumbling around randomly (and this goes against every web-intuitive I've developed in the last 6 years), do yourself (and me) a favor and just download the whole damn thing. Last but not least (I think?), its a Wiki. And its GNU. Its GNU-Wiki! That means its (almost) as much mine as yours in rights *and* access. Anyone can come along and edit anything. If you hate something, fix it. If you have a comment, log it. If you have hate, fix me with a comment. You get the idea. I feel like one of those street lunatics that makes such an eccentric performance that everyone goes out of their way *not* to notice him. 150 pages in, I've gotten *0* feedback before the "excellent" I just now stumbled across =)