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,FREEMAIL_FROM autolearn=ham autolearn_force=no version=3.4.4 X-Google-Thread: 103376,7b0188e023be40b6 X-Google-Attributes: gid103376,domainid0,public,usenet X-Google-Language: ENGLISH,ASCII-7-bit Path: g2news2.google.com!postnews.google.com!q9g2000yqc.googlegroups.com!not-for-mail From: roderick.chapman@googlemail.com Newsgroups: comp.lang.ada Subject: Re: SPARK Examiner -- visibility of Ada.Strings.Unbounded (and probably lots of other packages) Date: Fri, 27 Mar 2009 01:34:08 -0700 (PDT) Organization: http://groups.google.com Message-ID: <92db8dce-c32b-4938-9c00-f8a98261edef@q9g2000yqc.googlegroups.com> References: <8c753bd7-3df6-418a-8cd7-342af6eadeff@g38g2000yqd.googlegroups.com> <49cb9cd8$0$31344$9b4e6d93@newsspool4.arcor-online.net> <7VPFzoBF4IzJJwYX@diphi.demon.co.uk> NNTP-Posting-Host: 217.205.167.137 Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Trace: posting.google.com 1238142849 2031 127.0.0.1 (27 Mar 2009 08:34:09 GMT) X-Complaints-To: groups-abuse@google.com NNTP-Posting-Date: Fri, 27 Mar 2009 08:34:09 +0000 (UTC) Complaints-To: groups-abuse@google.com Injection-Info: q9g2000yqc.googlegroups.com; posting-host=217.205.167.137; posting-account=HCzrEgkAAABSfGsTnv-u5wET6EzuneVi User-Agent: G2/1.0 X-HTTP-UserAgent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-GB; rv:1.9.0.7) Gecko/2009021910 Firefox/3.0.7,gzip(gfe),gzip(gfe) Xref: g2news2.google.com comp.lang.ada:5330 Date: 2009-03-27T01:34:08-07:00 List-Id: Yeah - to process Bar, the Examiner needs to have previously seen (or at least know where to find) the specification of Foo. There's no "default" way to do this, since the Examiner is designed to deal with the program-library structure and naming scheme of _any_ Ada compiler - we can't just assume that people name their compilation units and files like GNAT prefers to, for example. So...you either need to specify both files on the command line - this works for small example but rapidly becomes tedious! e.g. spark bar.ads foo.ads The better solution is to add Bar and Foo to the Examiner's "Index file" - this establishes a mapping from compilation unit to filenames that the Examiner can use to automatically find the specifications of other units. The index file is set by the -index option so if it says -index=spark, then you need to add the following two lines to the spark.idx file foo spec is in foo.ads bar spec is in bar.ads OR...you can use the "sparkmake" tool to generate the index file for you automatically from a group of files. More details in the book chapter 9 and section 4 of the Examiner User Manual (which you should have - Examiner_UM.pdf). I strongly recommend that you read through at least the first 4 chapters of the Examiner User Manual - full of useful info I promise! :-) All the best, Rod