| How to support Oracle Pro C/C++ syntax within CDT [message #1747510] |
Tue, 15 November 2016 15:07  |
 Guillaume Ame
Messages: 2
Registered: November 2016 |
Junior Member |
|
|
I'm trying to setup a project that uses Pro C/C++ extensively.
That means that nearly all methods are stuffed with lines like these:
EXEC SQL BEGIN DECLARE SECTION ;
or
EXEC SQL
SELECT count(*)
INTO :nbProgramme
FROM GAdefProg
WHERE UPPER(cdProgramme) = UPPER(:ctxVarWeb.ctx_paramC3);
I can add a #ifdef #endif around each of these lines, but my conservative co-workers would like to keep their decades long habits.
Is their any way to tell CDT to ignore some pattern in the sources ?
If there's no way to perform this action, how hard would it be to add the feature in CDT code base for someone that never wrote any plugin for eclipse ?
[Updated on: Wed, 16 November 2016 11:19] Report message to a moderator |
|
|
| Re: How to support Oracle Pro C/C++ syntax within CDT [message #1747566 is a reply to message #1747510] |
Wed, 16 November 2016 01:26  |
David Vavra
Messages: 1426
Registered: October 2012 |
Senior Member |
|
|
You could try adding Indexer preprocessor macros (mostly defined as having no value or maybe just ';')
Could be tedious if there are a lot of them
If you're lucky there may be only one or two that need be defined which would effectively surround the rest with #if ... #endif
Three are two ways to enter an Indexer macro:
Project --> Properties --> C/C++ General --> Preprocessor Includes, Macro, etc. as a User Entry
Project --> Properties --> C/C++ General --> Paths and Symbols under the Symbols tab.
The first way provides for using a preprocessor macros file. Never tried it though.
You would also have to do this for each project.
[Updated on: Wed, 16 November 2016 01:52] Report message to a moderator |
|
|
|
|
|
Powered by
FUDForum. Page generated in 0.03079 seconds
] 
Search
Help
Register
Login
Home
