9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Stephen Parker <stephen.parker@pitechnology.com>
To: "'9fans@cse.psu.edu'" <9fans@cse.psu.edu>
Subject: RE: [9fans] don't shoot me
Date: Mon, 21 Jul 2003 16:40:04 +0100	[thread overview]
Message-ID: <E562FCEE3A42D61192880002A5FB43330107C795@KITE> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 217 bytes --]

"Modern C++ Design" (Andrei Alexandrescu) takes this extra step and attempts to
implement patterns using templates.  If you thought C++ had already gone too far
then this book should confirm this.

stephen




[-- Attachment #1.2: Type: text/html, Size: 696 bytes --]

[-- Attachment #2: Re: [9fans] don't shoot me --]
[-- Type: message/rfc822, Size: 2844 bytes --]

[-- Attachment #2.1.1: Type: text/plain, Size: 754 bytes --]

> I don't think it has much to do with XML, but "design patterns"
> are a genuine advancement in the field of software engineering,
> applicable only with support from object-oriented languages,

Come on.  ``Genuine advancement in the field of software engineering''
is a bit strong.  As Gamma et al themselves point out in the
introduction, nothing in the book is new.  The only advancement they
made was to package them up in one place and give names everyone could
use as the basis for a common vocabulary.

> in the case of C++ using templates to implement the patterns.

Funny, most of the design patterns in Gamma et al don't use templates.
Only four or five out of 23 do.  Most just use simple inheritence
hierarchies.

	- Dan C.

[-- Attachment #2.1.2: Type: text/html, Size: 1471 bytes --]

             reply	other threads:[~2003-07-21 15:40 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-21 15:40 Stephen Parker [this message]
     [not found] <1627809308@snellwilcox.com>
2003-07-18 17:00 ` steve.simon
  -- strict thread matches above, loose matches on Subject: below --
2003-07-18 15:45 Trickey, Howard W (Howard)
2003-07-18 15:12 pac
2003-07-18 15:17 ` Lucio De Re
2003-07-18 19:15   ` Scott Schwartz
2003-07-18 19:34     ` ron minnich
2003-07-18 20:34       ` Dan Cross
2003-07-18 21:10         ` boyd, rounin
2003-07-18 21:51           ` Skip Tavakkolian
2003-07-18 21:58             ` boyd, rounin
2003-07-21  8:28           ` Douglas A. Gwyn
2003-07-21  8:50             ` boyd, rounin
2003-07-21 15:09             ` Dan Cross
2003-07-18 21:13         ` boyd, rounin
2003-07-18 15:17 ` ron minnich
2003-07-18 15:23 ` Fco.J.Ballesteros
2003-07-18 15:50   ` Dave Lukes
2003-07-18 17:43     ` boyd, rounin
2003-07-19  3:12     ` Geoff Collyer
2003-07-19  3:45       ` Dan Cross
2003-07-19  3:48         ` boyd, rounin
2003-07-19  4:11           ` Dan Cross
2003-07-19  4:15             ` boyd, rounin
2003-07-21  8:28           ` Anthony Mandic
2003-07-21  8:57             ` boyd, rounin
2003-07-19  4:18         ` boyd, rounin
2003-07-19  4:20         ` Geoff Collyer
2003-07-19  4:26           ` boyd, rounin
2003-08-12 16:09       ` jared jennings
2003-07-18 16:55 ` David Presotto
2003-07-18 17:02   ` ron minnich
2003-07-18 18:22     ` Nigel Roles
2003-07-21  8:27     ` Anthony Mandic
2003-07-18 17:10 ` matt
2003-07-19  6:45 ` Taj Khattra
2003-07-19  6:51   ` boyd, rounin
2003-07-19 11:19     ` Bruce Ellis
2003-07-19 11:41       ` boyd, rounin

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=E562FCEE3A42D61192880002A5FB43330107C795@KITE \
    --to=stephen.parker@pitechnology.com \
    --cc=9fans@cse.psu.edu \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).