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=0.2 required=5.0 tests=BAYES_00,INVALID_MSGID, REPLYTO_WITHOUT_TO_CC autolearn=no autolearn_force=no version=3.4.4 X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 103376,899484222880ae7c X-Google-Attributes: gid103376,public From: Tom Moran Subject: Re: preventing inheritance Date: 1996/12/16 Message-ID: <32B640FC.D30@bix.com>#1/1 X-Deja-AN: 204530309 references: <32B22CDC.3FE4@bix.com> <32B5A234.947@watson.ibm.com> content-type: text/plain; charset=us-ascii organization: InterNex Information Services 1-800-595-3333 mime-version: 1.0 reply-to: tmoran@bix.com newsgroups: comp.lang.ada x-mailer: Mozilla 3.0Gold (Win95; I) Date: 1996-12-16T00:00:00+00:00 List-Id: >Create abstract S and derive T and U from it I could do this but it will look rather bizarre. Type T is an MS Windows Edit control and type U is a multiline Edit control. Operation B is 'get first visible character horizontally' for the single line edit control, but the corresponding multiline operation is to get the first visible line vertically. Other than that, it's always reasonable to have one operation which either is identical for single/multiline edit boxes, and thus can be inherited, or two operations which have obviously analogous, if not identical, interpretations, and thus need over-riding. Several ways of getting around this annoyance have been suggested, but none seems likely to cause a user to look and say 'obviously, that's the only reasonable organization'.