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=ham autolearn_force=no version=3.4.4 X-Google-Thread: 103376,714a40eb8c53061d X-Google-NewGroupId: yes X-Google-Attributes: gida07f3367d7,domainid0,public,usenet X-Google-Language: ENGLISH,ASCII-7-bit Path: g2news1.google.com!news1.google.com!news.glorb.com!feeder.erje.net!feeder.news-service.com!aioe.org!.POSTED!not-for-mail From: Simon Wright Newsgroups: comp.lang.ada Subject: Re: ADA and Open GL Date: Wed, 10 Aug 2011 12:09:52 +0100 Organization: Aioe.org NNTP Server Message-ID: References: <4e4144df$0$2573$703f8584@news.kpn.nl> <4e424822$0$2559$703f8584@news.kpn.nl> NNTP-Posting-Host: SptRn4/nB6/EZ1vi/h8RlA.user.speranza.aioe.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Complaints-To: abuse@aioe.org User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.3 (darwin) X-Notice: Filtered by postfilter v. 0.8.2 Cancel-Lock: sha1:skg1BE4fE/AtUzO/NErmpTXWszw= Xref: g2news1.google.com comp.lang.ada:20506 Date: 2011-08-10T12:09:52+01:00 List-Id: "ldries46" writes: > My program seems correct now, but I get the following error message: > > opengl-glu.ads:373:31: warning: subprogram pointer > "gluNurbsCallback.CallBackFunc" should have foreign convention > opengl-glu.ads:373:31: warning: add Convention pragma to declaration > of "GLU.GLUFUNCPTR" at line 231 > > This is found in a standard unit nl. the adabindings to Open GL, GLU > and GLUT > > Can I disregard this warning or should I do something to avoid it. I > don't thoink I should be altering my copy of the ADA bindings so > where should I do something. > In my program I don't call this routine directly soit is a result of a > call from another routine within the ADA bindings. Perhaps you're compiling with a different set of compiler options than those used by the developer of the bindings? Very often, GNAT will in fact translate iffy code like this correctly (the compiler backend understands C, of course). Better not to risk it, though, convention errors can be a real pain to debug. Those bindings aren't "standard" in the RM sense. Personally I'd make the change and send a patch to the bindings maintainer.