Return to the
comp.compilers page.
Search the
comp.compilers archives again.
| From: | anton@mips.complang.tuwien.ac.at (Anton Ertl) |
| Newsgroups: | comp.compilers |
| Date: | Tue, 10 Apr 2018 05:48:43 GMT |
| Organization: | Institut fuer Computersprachen, Technische Universitaet Wien |
| References: | <49854345-f940-e82a-5c35-35078c4189d5@gkc.org.uk> 18-03-103 18-03-042 18-03-047 18-03-075 18-03-079 18-03-101 18-04-002 18-04-003 18-04-004 |
| Injection-Info: | gal.iecc.com; posting-host="news.iecc.com:2001:470:1f07:1126:0:676f:7373:6970"; logging-data="53088"; mail-complaints-to="abuse@iecc.com" |
| Keywords: | history, design |
| Posted-Date: | 10 Apr 2018 11:09:17 EDT |
George Neuner <gneuner2@comcast.net> writes:
>The necessity to write "Design Patterns" was, IMO, acknowledgement
>that the average programmer could not figure out how to express their
>ideas under Java's limited object model.
Design Patterns was published in 1994 (based on work that started in
1990), before Java was published in 1995. Moreover, it says at the
beginning that the design patterns are somewhat language-specific, and
that the language they have in target is C++. It seems to me to be
more a guideline of how to make use of the vast possibilities of a
programming language to achieve certain things effectively (and with
maintainable results), rather than a guideline on how to work around
limitations.
- anton
--
M. Anton Ertl
anton@mips.complang.tuwien.ac.at
http://www.complang.tuwien.ac.at/anton/
Return to the
comp.compilers page.
Search the
comp.compilers archives again.