From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me X-Spam-Level: X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00 autolearn=ham autolearn_force=no version=3.4.4 X-Google-Thread: 103376,131f06967722ab4b X-Google-Attributes: gid103376,public X-Google-Language: ENGLISH,ASCII-7-bit Path: g2news1.google.com!news4.google.com!news.glorb.com!border1.nntp.dca.giganews.com!nntp.giganews.com!local1.nntp.dca.giganews.com!nntp.rcn.net!news.rcn.net.POSTED!not-for-mail NNTP-Posting-Date: Tue, 21 Dec 2004 15:16:34 -0600 Sender: jsa@rigel.goldenthreadtech.com Newsgroups: comp.lang.ada Subject: Re: Ada 2005? References: <1103344064.372396.51420@c13g2000cwb.googlegroups.com> <1n1v6175zrtcc.2g6ewdvu7ei5$.dlg@40tude.net> <1103568585.285484.237450@c13g2000cwb.googlegroups.com> <20xbhf8rjd33.t7dojmf0ky12.dlg@40tude.net> <1nl7gq6tozeyw.146x7at50m0lr.dlg@40tude.net> <1vj2pp9437gal.1b1lyqe3o973k$.dlg@40tude.net> From: jayessay Organization: Tangible Date: 21 Dec 2004 16:42:58 -0500 Message-ID: User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.2 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii NNTP-Posting-Host: 209.6.25.79 X-Trace: sv3-LfrQDi159Dv3Q7+V5Do2oziwGJiXVm4XTHzaWuxq0ieqLH59S1LPEYVgl2c7OIjkZz1A4PGWWDhQiFm!oD7a6Nr1a1Mw37rQKWyBbPfoTcfXDeM66HmBSlEEz91anIcgJRPDKEytGOpL5CCF3Q6VbzXX4d8P X-Complaints-To: abuse@rcn.net X-DMCA-Complaints-To: abuse@rcn.net X-Abuse-and-DMCA-Info: Please be sure to forward a copy of ALL headers X-Abuse-and-DMCA-Info: Otherwise we will be unable to process your complaint properly X-Postfilter: 1.3.22 Xref: g2news1.google.com comp.lang.ada:7130 Date: 2004-12-21T16:42:58-05:00 List-Id: "Dmitry A. Kazakov" writes: > On 21 Dec 2004 12:10:21 -0500, jayessay wrote: > > > 1. For an example of of multiple dispatch, see generic functions, > > method resolution and dispatch in CLOS: > > > > http://www.lispworks.com/reference/HyperSpec/Body/07_f.htm > > http://www.lispworks.com/reference/HyperSpec/Body/07_ff.htm > > The problem with MD is not target method resolution, which is quite > trivial, but safety in presence of inheritance with combinatorial > explosion of target methods to override Method combination and consistency is part of method resolution by any reasonable assesment. > I doubt that CLOS seriously approaches the problem. That's an odd statement, and it is just uninformed opinion which happens to be factually incorrect. If you really would like to understand the issues you should read the hyperspec sections noted above as a start. This will give you a programmer's (user's) view of things albeit from a language specification angle. More information as to the what, hows, and wherefores can be found in (1) and further insight and rationale is detailed in the MOP (2). It's worth noting that CLOS method combination is actually programmable. There are several versions supplied as part of the specification (including the 'standard method combination'), but the protocol and semantics of how to define others is also defined and specified. /Jon 1. Common Lisp the Language, second edition; Guy Steele 2. The Art of the Metaobject Protocol; Gregor Kiczales, Jim Rivieres, Daniel Bobrow -- 'j' - a n t h o n y at romeo/charley/november com