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=0.2 required=5.0 tests=BAYES_00,INVALID_MSGID,
	REPLYTO_WITHOUT_TO_CC autolearn=no autolearn_force=no version=3.4.4
X-Google-Language: ENGLISH,ASCII-7-bit
X-Google-Thread: 103376,c9bab6e4b2f263f2,start
X-Google-Attributes: gid103376,public
From: lance@eco.twg.com (Lance Kibblewhite)
Subject: GNAT 3.09, NT, and error messages
Date: 1997/01/29
Message-ID: <32ef9026.417742161@library.airnews.net>#1/1
X-Deja-AN: 213029711
content-type: text/plain; charset=us-ascii
organization: Attachmate
mime-version: 1.0
reply-to: lance@eco.twg.com
newsgroups: comp.lang.ada
Date: 1997-01-29T00:00:00+00:00
List-Id: <comp.lang.ada>


Previous versions of the NT port of GNAT (3.04 and earlier) would
generate compiler error messages in a format that was compatible with
the Visual C++ IDE, in that the IDE was able to pull up the
appropriate file, and hi-light the offending line just as it could
with C/C++.

Version 3.09 error messages do not appear to be in the appropriate
format to allow this.

Was it simply fortuitous that this previously worked?

Would it be possible to add this feature back into a future release,
perhaps as a compiler option?

-- Lance.