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,73975695cdfcb86f X-Google-NewGroupId: yes X-Google-Attributes: gida07f3367d7,domainid0,public,usenet X-Google-Language: ENGLISH,ASCII-7-bit Received: by 10.68.125.233 with SMTP id mt9mr1578352pbb.5.1333805294308; Sat, 07 Apr 2012 06:28:14 -0700 (PDT) Path: r9ni29097pbh.0!nntp.google.com!news2.google.com!npeer02.iad.highwinds-media.com!news.highwinds-media.com!feed-me.highwinds-media.com!nx01.iad01.newshosting.com!newshosting.com!news-out.readnews.com!transit3.readnews.com!panix!newsfeed-00.mathworks.com!nntp.TheWorld.com!.POSTED!not-for-mail From: Robert A Duff Newsgroups: comp.lang.ada Subject: Re: Dispatching callback handed over to C Date: Sat, 07 Apr 2012 09:28:13 -0400 Organization: The World Public Access UNIX, Brookline, MA Message-ID: References: <6fb83c74-b2a4-4ae8-9c89-d755b737198f@v22g2000vby.googlegroups.com> <85d1ad51-c02b-44fa-87b6-02aa1d8ba1b2@x17g2000vba.googlegroups.com> <62246369-6b9f-4a96-9c67-fd1774c02e78@k24g2000yqe.googlegroups.com> NNTP-Posting-Host: shell01.theworld.com Mime-Version: 1.0 X-Trace: pcls6.std.com 1333805293 26929 192.74.137.71 (7 Apr 2012 13:28:13 GMT) X-Complaints-To: abuse@TheWorld.com NNTP-Posting-Date: Sat, 7 Apr 2012 13:28:13 +0000 (UTC) User-Agent: Gnus/5.1008 (Gnus v5.10.8) Emacs/21.3 (irix) Cancel-Lock: sha1:hJ3CQkYG3bQXT9MzR9O44C7nxq8= X-Received-Bytes: 2258 Content-Type: text/plain; charset=us-ascii Date: 2012-04-07T09:28:13-04:00 List-Id: Simon Wright writes: > Natasha Kerensikova writes: > I think that must be it. That's right. If you're not doing anything with these things on the C side, except copying the pointers around, then it's fine to silence the warning. Use the form of pragma Warnings(Off/On) with a string around that one line of code, so you only silence the one warning. There's nothing wrong with silencing warnings when they are false alarms, although it's a good idea to have a comment explaining why. >...I did wonder whether a classwide pointer might > be a fat pointer, ... GNAT never uses fat pointers for class-wide. Fat pointers are used only when the designated type is an unconstrained array (and there are ways to get thin pointers for arrays). I am ignoring access-to-subprogram, here. - Bob