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,c6e016ae58737f34
X-Google-Attributes: gid103376,public
From: Mats Weber <Mats.Weber@elca-matrix.ch>
Subject: Re: win32ada design question/problem
Date: 1998/11/23
Message-ID: <3659963D.1D186DDF@elca-matrix.ch>#1/1
X-Deja-AN: 414850579
Content-Transfer-Encoding: 7bit
References: <731rn7$kj5@lotho.delphi.com> <7324a6$4fs$1@nnrp1.dejanews.com>
 <3654a7f3.11586041@news.pacbell.net> <36598497.CD4BDD47@flinet.com>
X-Accept-Language: en
Content-Type: text/plain; charset=us-ascii
Organization: ELCA Matrix SA
Mime-Version: 1.0
Reply-To: Mats.Weber@elca-matrix.ch
Newsgroups: comp.lang.ada
Date: 1998-11-23T00:00:00+00:00
List-Id: <comp.lang.ada>

Marin David Condic wrote:

> [...] Here' I'd like to have a slightly meatier interface than the
> Win32Ada interface which simply organized the types and parameters the way an
> Ada programmer would expect to see them, then having the binding translate to
> the low level Win32Ada code. Maybe we call it Win32Ada++?)

The problem with this beautiful idea is that it is never going to
happen. Look at POSIX 1003.5: it's hard to find a working implementation
even now, years after the IEEE standard was accepted. People just can't
wait for such bindings to come out, so I think we must still produce
thin automatically generated bindings so that they become available
shortly after the product that they interface. This is especially true
for Windows, which changes very often.