| urgent: #ifdef parsing [message #79432] |
Sun, 31 August 2003 21:57  |
Eclipse User |
|
|
|
Originally posted by: Michael.Xiong.chn.xerox.com
I use CDT to view a C project.
There're some functions written like this:
#ifdef __STDC__
void FooBar(Foo foo, Bar bar)
#else
void FooBar(foo, bar)
Foo foo;
Bar bar;
#endif /* __STDC__ */
{
}
but in outline panel, they are not recognized as functions, but only show
as variables 'foo' and 'bar'.
This take inconvience to me.
Is it a bug of CDT? Or can I correct it by some configuration of CDT
enviroment?
It's urgent for me.
Thanks for any helping!
Michael
2003/9/1
|
|
|
|
|
|
| Re: urgent: #ifdef parsing [message #79754 is a reply to message #79465] |
Thu, 04 September 2003 10:42  |
| Eclipse User |
|
|
|
Parsing in the CDT is still somewhat immature, we're working on trying to
get those features to work in a compiler-agnostic way in a market that is
heavily fragmented and non-ANSI compliant.
"Michael Xiong" <Michael.Xiong@chn.xerox.com> wrote in message
news:biunhv$690$1@eclipse.org...
> It seems that I have to add
> #ifndef __STDC__
> #define __STDC_
> #endif
> on every head of .c files?
>
> That's too tedius!
>
> I've tried to add only a #define __STDC__ to a "xxxcommon.h", but no
> effect.
> I think CDT should provide a configuration place to set common predefined
> macros, shoud it?
>
> > I use CDT to view a C project.
>
> > There're some functions written like this:
>
> > #ifdef __STDC__
> > void FooBar(Foo foo, Bar bar)
> > #else
> > void FooBar(foo, bar)
> > Foo foo;
> > Bar bar;
> > #endif /* __STDC__ */
> > {
> > }
>
> > but in outline panel, they are not recognized as functions, but only
show
> > as variables 'foo' and 'bar'.
>
> > This take inconvience to me.
>
> > Is it a bug of CDT? Or can I correct it by some configuration of CDT
> > enviroment?
>
> > It's urgent for me.
> > Thanks for any helping!
>
> > Michael
> > 2003/9/1
>
>
|
|
|
Powered by
FUDForum. Page generated in 0.05651 seconds
Home