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.3 required=5.0 tests=BAYES_00,INVALID_MSGID autolearn=no autolearn_force=no version=3.4.4 X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 103376,6cd0753a57f9edec X-Google-Attributes: gid103376,public From: stt@houdini.camb.inmet.com (Tucker Taft) Subject: Re: Resolution of Dispatching Operations Date: 1997/02/26 Message-ID: #1/1 X-Deja-AN: 221658504 Sender: news@inmet.camb.inmet.com (USENET news) X-Nntp-Posting-Host: houdini.camb.inmet.com References: Organization: Intermetrics, Inc. Newsgroups: comp.lang.ada Date: 1997-02-26T00:00:00+00:00 List-Id: Matthew Heaney (mheaney@ni.net) wrote: : I have a question about the rules for resolution of (dispatching) operations. : I have a type with 2 operations that differ only with respect to whether : the arguments are class-wide or specific: : procedure Op (L : in T; R : in out T'Class); : procedure Op (L : in T'Class; R : in out T); : If I'm in a context where I have 2 class-wide objects and I call Op, which : version of Op gets called? Like this : declare : O1, O2 : T'Class; : begin : Op (O1, O2); : end; : On my compiler, the first version gets called, but I have no idea why that : one would be favored over the other. The compiler has a bug. It should report the call (at compile-time) as being ambiguous. : My expectation is that at some point, either at compile-time or at : run-time, I would get an error that says the compiler couldn't figure out : which operation I meant. What am I missing? A bug-free compiler ;-). : ... : Matthew Heaney : Software Development Consultant : : (818) 985-1271 -Tucker Taft stt@inmet.com http://www.inmet.com/~stt/ Intermetrics, Inc. Burlington, MA USA