home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.databases.oracle
- Path: sparky!uunet!zaphod.mps.ohio-state.edu!cis.ohio-state.edu!magnus.acs.ohio-state.edu!csn!news.den.mmc.com!crowded-house!richard
- From: richard@crowded-house.den.mmc.com (Richard Armstrong)
- Subject: Pro*C
- Message-ID: <1992Dec17.195431.13161@den.mmc.com>
- Sender: news@den.mmc.com (News)
- Nntp-Posting-Host: crowded-house.den.mmc.com
- Organization: Martin Marietta
- Date: Thu, 17 Dec 1992 19:54:31 GMT
- Lines: 35
-
-
- I have plenty of good things to say about Oracle Pro*C. However, let me
- focus on one area where I find Pro*C completely brain-dead.
-
- I am running v6 on Sun 690's.
-
- Why doesn't the Pro*C precompiler do #define substitutions? For instance,
- one cannot do the following:
-
- #define MAXLEN 80
-
- EXEC SQL BEGIN DECLARE SECTION;
- varchar string[MAXLEN + 1];
- EXEC SQL END DECLARE SECTION;
-
- Pro*C doesn't like MAXLEN, so I run the C pre-processor to do the substitution,
- but then Pro*C doesn't like the [80 + 1]. So I had to write my own pre-
- processor to do the math.
-
- I have a solution, but it requires running cpp, and my own custom pre-processor,
- and then finally running Pro*C. Does this seem lame to anyone besides me?
-
- Is this fixed in v7? I am stuck with v6 for now... Does anyone have a fix
- to this better than what I came up with?
-
- This is my only real show-stopper complaint with Pro*C.
-
- Any input is appreciated.
-
-
- --
- My company never said any of this... I didn't either.
- Richard Armstrong, Software Engineer, Martin Marietta
- Email->>>> richard@crowded-house.den.mmc.com <<<<-Email
-
-