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,a89010748f152206 X-Google-Attributes: gid103376,public From: tmoran@bix.com Subject: Re: Is There A Newer Win32Ada For ObjectAda? Date: 2000/02/05 Message-ID: #1/1 X-Deja-AN: 581766388 References: X-Complaints-To: abuse@pacbell.net X-Trace: nnrp2-w.snfc21.pbi.net 949715437 206.170.2.87 (Fri, 04 Feb 2000 17:50:37 PST) Organization: SBC Internet Services NNTP-Posting-Date: Fri, 04 Feb 2000 17:50:37 PST Newsgroups: comp.lang.ada Date: 2000-02-05T00:00:00+00:00 List-Id: >The Win32Ada packages, or at least the ones that come with ObjectAda, >are out of date. I need some of the Win32 facilities that are not >available in the ObjectAda version of Win32Ada. >... >Frankly, I would rather not switch from Win32Ada to WinAPI. I already >have a lot of code using Win32Ada that would have to be revised. It perhaps bears repeating that selecting a binding to something as large as Windows should be done only after careful thought, and with a view toward future needs. Something that seems adequate, and cheap and easy to start using, may lock you into a particular binding or compiler and be very painful to change in the future. Tom Moran (who has contributed to making CLAW over 5MB of Ada-style binding, containing "pragma import"s for over 500 Windows functions, plus examples and docs)