🚀 go-pugleaf

In article <1993Aug9.202554.25804@schaefer.math.wisc.edu> horn@schaefer.math.wisc.edu (Jeffrey Horn) writes:
>Can one successfully compile and link an ESQL/C program under MS-DOS
>using the currently, commercially available MS Visual C/C++ (MS C version 7.0)?
>The manuals that come with the MS-DOS version of ESQL/C state that one
>must use Microsoft C version 6.  It is unclear whether this is the minimum
>version or whether later version will not work.  So far I cannot find Microsoft
>C version 6.0 in stores in my area, so if the current version of MS C is
>not supported I have a real problem.
>

I think you should not have any particular problems to preprocess your
ESQL statement if you are writing C code. If you are using C++ it would
be different. (Providing that you could link an old version library to
the new executable.) Two main reasons are -

1. The syntax is different.
2. The rules of name generation in object files are different.

>By the way, why is Ingres tied so closely to a single C compiler?  Why not
>support other popular PC C compilers (Borland, Zoratech, etc.)?  Do these
>compilers in fact work and Ingres just doesn't want to have to do tech
>support on them, or what?
>

I think that you're right and this is a support problem. The library format
and startup modules are slightly different, say, for MSC and Borland C, so
Ingres should provide a special library for every compiler.

>Thanks,
>
>Jeff Horn
>

My opinion only.

Michael
--
Michael Haldey  |  Genasys II Pty Ltd, Sydney, Australia
                |  Internet: michaelh@g2syd.genasys.com.au
		|
		|  #include  <std_disclaimer.h>

In article <1993Aug10.235351.20218@g2syd.genasys.com.au> michaelh@g2syd.genasys.com.au (Michael Haldey) writes:
...
>
>I think you should not have any particular problems to preprocess your
>ESQL statement if you are writing C code. If you are using C++ it would
>be different. (Providing that you could link an old version library to
		^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Sorry, this statement should follow the first one. :)

>the new executable.) Two main reasons are -
>
Michael
--
Michael Haldey  |  Genasys II Pty Ltd, Sydney, Australia
                |  Internet: michaelh@g2syd.genasys.com.au
		|
		|  #include  <std_disclaimer.h>

I recently spoke to an Ingres Senior Engineer and his solution for using
ESQL/C with C++ was:
	Preprocess and compile all of your ESQL/C and then call the compiled
        C functions from within your C++ program.  Apparently their
        preprocessor on UNIX cannot handle C++ code.

        You may be interested to know that Ingres is releasing their
        Client side API in 1994.