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-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 103376,95a5884373f97767,start X-Google-Attributes: gid103376,public X-Google-ArrivalTime: 2001-08-11 13:52:47 PST Path: archiver1.google.com!newsfeed.google.com!newsfeed.stanford.edu!canoe.uoregon.edu!arclight.uoregon.edu!enews.sgi.com!newshub2.rdc1.sfba.home.com!news.home.com!news1.rdc2.pa.home.com.POSTED!not-for-mail From: "Harry Henry Gebel" Subject: Portability of 'pragma Assert' Newsgroups: comp.lang.ada Message-ID: <20010811.165244.1244316437.14108@elroy.house> User-Agent: Pan/0.9.6 (Unix) Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Date: Sat, 11 Aug 2001 20:53:02 GMT NNTP-Posting-Host: 65.1.163.99 X-Complaints-To: abuse@home.net X-Trace: news1.rdc2.pa.home.com 997563182 65.1.163.99 (Sat, 11 Aug 2001 13:53:02 PDT) NNTP-Posting-Date: Sat, 11 Aug 2001 13:53:02 PDT Organization: Excite@Home - The Leader in Broadband http://home.com/faster Xref: archiver1.google.com comp.lang.ada:11797 Date: 2001-08-11T20:53:02+00:00 List-Id: I am writing a library and would like to make sure it is portable, but I only have access to gnat, so I can't actually test it's portability (until it is working to the point where I can upload it at any rate.) I would like to use gnat's 'pragma Assert' and want to make sure it is portable. My reading of the ARM seems to say that a compiler that does not have 'pragma Assert' will simply ignore it, so I'm not to concerned with any compiler like that. However, searching the news group archives turned up references to other compilers that use 'pragma Assert' and my concern is that if those compilers have the pragma but use it differently it could cause compilation to fail. Is this a valid concern or are other compiler's 'pragma Assert's compatible with gnat's? The only reference to incompatibility I found said to make sure the assertion is placed in a part of the code where you would normally have a statement; I have done this. Is it neccessary to do anything else to keep assertions compatible across different compilers? -- Harry Henry Gebel West Dover Hundred, Delaware GPG encrypted email gladly accepted. Key ID: B853FFFE Fingerprint: 15A6 F58D AEED 5680 B41A 61FE 5A5F BB51 B853 FFFE