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,c3bb5e0c8d486559,start X-Google-Attributes: gid103376,public From: gvc@ocsystems.com (G. Vincent Castellano) Subject: Re: Programming X Windows... Date: 1996/10/22 Message-ID: <1996Oct22.171704.25522@ocsystems.com>#1/1 X-Deja-AN: 191286455 organization: OC Systems, Inc. newsgroups: comp.lang.ada Date: 1996-10-22T00:00:00+00:00 List-Id: % % I have never seen a thin Ada binding I liked, although I will admit % to not having seen bindings from many sources. The ones I have seen % seem to be done "on the cheap" with no attempt to use derived numeric % types to separate the "number of apples" cells from the "number of % oranges" cells. % First, with Ada 95's general access types, modular types and access to subprograms, it is much easier to create thin bindings whose typing corresponds reasonably closely to the original interface. Have you looked at any Ada 95 bindings? Second, the determination of how and where to define derived types is often impossible to determine from the 'original text' of the interface you're binding to. If the interface was not originally designed with the subtype/derived type issue in mind, it's pretty tough to graft one on as an afterthought. ----------------------------------------------------------------------- - G. Vincent Castellano, Sr. Software Engineer, OC Systems Inc - - gvc@ocsystems.com :: X/Ada WWW => http://www.ocsystems.com/xada - ----------------------------------------------------------------------- - "If virtual memory did not exist, it would - - have become necessary for us to invent it." - -----------------------------------------------------------------------