Path: utzoo!attcan!uunet!lll-winken!ames!pacbell!rtech!squid!robf
From: robf@squid.rtech.com (Robert Fair)
Newsgroups: comp.databases
Subject: Re: Ingres ESQL/C users: try this script!
Message-ID: <2966@rtech.rtech.com>
Date: 8 Jun 89 15:09:55 GMT
References: <GNB.89Jun6131501@baby.bby.oz>
Sender: news@rtech.rtech.com
Reply-To: robf@squid.UUCP (Robert Fair)
Distribution: comp
Organization: Relational Technology, Inc.
Lines: 28


gnb@bby.oz (Gregory N. Bond) writes:

>2) Any errors in the C code that are caught by the c compiler are
>reported as errors in the C file.  The line numbers etc don't
>correspond very well to the input .sc file, making it dificult to find
>the bug in the original program.  What's even worse, things like
>error(1) and GNUEmacs next-error function (C-X `) jump to the wrong
>file.  What's even worser (!) the info needed to tell the C compiler
>about lines and files and guff is all included in comments in the
>preprocessed C file, but not presented as "#line": directives.

and presents a utility to make real #line comments. A much easier way
of doing this is to make the ESQL/C compiler generate "#line" statements
directly !

To do this, just use the -# or -p precompiler flags, i.e.:

	esqlc -# myprog.sc

and then any C-compiler generated errors will be related directly back to
the .sc file, as gnb wants.

The -#/-p flags work in both INGRES 5.0 and 6.X, and are documented in
"ESQL Companion Guide for C" in the section on command line options.

Robert Fair
RTI Tech Support