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.3 required=5.0 tests=BAYES_00,INVALID_MSGID
	autolearn=no autolearn_force=no version=3.4.4
X-Google-Language: ENGLISH,ASCII-7-bit
X-Google-Thread: 103376,12283be683f6446b
X-Google-Attributes: gid103376,public
From: Matthew Heaney <matthew_heaney@acm.org>
Subject: Re: GNAT Stream Read processing problem
Date: 1999/01/06
Message-ID: <m3u2y4wipl.fsf@mheaney.ni.net>#1/1
X-Deja-AN: 429421616
Sender: matt@mheaney.ni.net
References: <76tsgd$s0o1@svlss.lmms.lmco.com>
 <76uv4j$njr$1@nnrp1.dejanews.com>
NNTP-Posting-Date: Wed, 06 Jan 1999 06:57:41 PDT
Newsgroups: comp.lang.ada
Date: 1999-01-06T00:00:00+00:00
List-Id: <comp.lang.ada>

dewar@gnat.com writes:

> Surely if you use -gnatv to point out the EXACT location of
> the error:
> 
>     30.          Long_Integer'Read(S, Data(ndx).elements);
>                                            |
>         >>> expected type "Standard.integer"
>         >>> found type "Standard.long_integer"
> 
> that should be enough of a clue, it is VERY specifically
> telling you that the subscript of Data must be of type
> Standard.integer, and you are using long_integer.
> 
> While you are learning Ada 95, use -gnatv as a matter of
> course to tell exactly where the error message is being
> posted. GNAT goes to great pains to try to post the error
> in exactly the most helpful place, take advantage of this!


If you use emacs with gnat, then C-x ` (the command "next-error") will
take you to the exact line and column containing the error.

Emacs is not just an editor, it's a way of life.  Ya know?