Re: New Pro*C 2.0 and C++

Tim Smith (tssmith_at_netcom.com) wrote: : jhalpin_at_netcom.com (Joe Halpin) writes:  

: >In article <tssmithCvw2DI.D8J_at_netcom.com> tssmith_at_netcom.com (Tim Smith) writes:
  [stuff deleted]

: >But you could just put all the Pro*C sections of the code into their own
: >(ANSI C) modules, then compile and link them with the C++ code, right?
: >Are there problems with Pro*C code being in different modules, (static
: >variables, etc)?
 

: I believe this is possible, but haven't actually done it myself.  

: --Tim (tssmith_at_netcom.com) (tssmith_at_oracle.com) (Not speaking for Oracle.)

We tried this with 1.5 and it did not work, tended to die in sqlexec calls to malloc etc. Oracle support eventually told me they didn't support this mixture (pro*C .o's and C++ .o's. ) and I had to do a quick c++->c translation to make our app work. We had too many other fires to fight to pursue the issue (with Oracle) then, but I'm about to try again with 2.0. If anyone has successfully mixed Pro*C and C++ (Solaris 2.x, Oracle 7) I would very much like to hear about it.

--
Carol A. Brown		        carol_at_majiq.com
MAJIQ Systems & Software    
Redmond, WA