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.9 required=5.0 tests=BAYES_00 autolearn=unavailable autolearn_force=no version=3.4.4 Path: eternal-september.org!reader01.eternal-september.org!reader02.eternal-september.org!feeder.eternal-september.org!nntp-feed.chiark.greenend.org.uk!ewrotcd!newsfeed.xs3.de!io.xs3.de!news.jacob-sparre.dk!franka.jacob-sparre.dk!pnx.dk!.POSTED.rrsoftware.com!not-for-mail From: "Randy Brukardt" Newsgroups: comp.lang.ada Subject: Re: Ada-Win32 bindings Date: Mon, 6 Aug 2018 16:57:33 -0500 Organization: JSA Research & Innovation Message-ID: References: <27b53953-36f2-4efe-b877-2e316b176d80@googlegroups.com> Injection-Date: Mon, 6 Aug 2018 21:57:34 -0000 (UTC) Injection-Info: franka.jacob-sparre.dk; posting-host="rrsoftware.com:24.196.82.226"; logging-data="6291"; mail-complaints-to="news@jacob-sparre.dk" X-Priority: 3 X-MSMail-Priority: Normal X-Newsreader: Microsoft Outlook Express 6.00.2900.5931 X-RFC2646: Format=Flowed; Original X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.7246 Xref: reader02.eternal-september.org comp.lang.ada:54070 Date: 2018-08-06T16:57:33-05:00 List-Id: Something else to link. - Randy wrote in message news:27b53953-36f2-4efe-b877-2e316b176d80@googlegroups.com... > Dear Ada community > > I am pleased to announce the initial release of ADA bindings for the Win32 > API > > Available at https://github.com/Alex-Gamper/Ada-Win32 > > These bindings where generated from the latest Windows SDK (version 17134) > on Windows 10 x64 and include the definitions that would be available from > the following C/C++ header file > > #include > #if (_MSC_VER >= 1900) > #ifdef _WIN64 > #if _WIN32_WINNT >= _WIN32_WINNT_WINBLUE > #include > #include > #include > #include > #include > #endif > #endif > #endif > > It is intended that these binding for the basis of both the Ada-WinRT > and the planned/future Ada-NetFramework bindings > > Note: Their is still a bit of work to do in these bindings, specifically > 1) Callbacks / function profiles need to be addressed (currently mapped to > System.Address) > 2) Handle inline functions ?? > 3) Better handling of Pre-processor macros ??