Using Eclipse CDT together with ORACLE PROC [message #690389] |
Wed, 29 June 2011 13:13 |
Markus Messages: 3 Registered: June 2011 |
Junior Member |
|
|
Dear Eclipse Community,
does anyone know- or has anyone ever used eclipse before together with Oracle PROC (Embedded SQL) ?
I'm working on a middle/large C/C++ Project which contains also a lot of embedded SQL Code. After configuring the Eclipse IDE, I can already work with it and iam very satisfied. Unfortunately, I can't find any settings to make the indexer either ignore the embedded SQL Code or accept it as it is. Therefore the IDE shows me a lot of syntax errors which seems to have an effect on the Indexer aswell. The Call Hierarchy view for example is not complete.
Can anyone give me an advice/solution for this issue? I would really love to get it to work
sincerely
Markus
[Updated on: Wed, 29 June 2011 13:13] Report message to a moderator
|
|
|
|
|
|
|
Re: Using Eclipse CDT together with ORACLE PROC [message #954173 is a reply to message #690805] |
Mon, 22 October 2012 21:08 |
Scott Bell Messages: 5 Registered: July 2009 |
Junior Member |
|
|
Axel,
I take it you are saying that the parsing rules are hard coded into the CDT plugin? Is or will there be any effort to externalize these? Pro*C is an extension to 'C' which is pretty common and promulgated by one of the largest companies in the known world (I actually don't like Oracle, but that's a personal thing and it would seem to be a very good thing to support it within the sphere of CDT and Eclipse.
I am not prepared to be able to change the code for the 'parser', but if there was an externalized ruleset, I could work with that.
Hmmm, while typing this, it brings up an interesting question...why can't the indexer use the same build process that builds actual code. In other words, if gcc can build Pro*C, and it can, then why can't Eclipse use gcc to index it? Maybe we are just missing something here and it already can!
This may be what the gist of Markus's was. It seems that a response of, "Then you will need to change the internal parser code..." may have been hasty. After all, CDT is a tool and should form itself to fit the need, rather than requiring needs to be modified to fit the tool
--Scott
|
|
|
Powered by
FUDForum. Page generated in 0.04091 seconds