On 6/9/11 11:58 AM, Andrew Johnson wrote:
> Comments/ideas? Just document it and ignore it?
Hi, Andrew.
My vote would be to fix the preprocessor; it shouldn't do that
substitution.
Why does using "vxWorks.h" work when <vxWorks.h> does not?
Because it thinks "vxWorks.h" is a C string constant and so
doesn't touch it?
I'm not the biggest fan of using "vxWorks.h". It's, as you
said, a workaround. When I read that, I think the author wrote
a vxWorks.h header file and wants to include it.
Your suggestion to adjust the sequencer's build rules seems like
an OK workaround if fixing the real problem is considered
undesirable.
I'm not a big fan of deleting the line completely. That just
makes it harder to understand how it works. I can no longer
just look at the source code. I'd have to look at the generated
build command at build time to figure out that vxWorks.h gets
included.
Lewis
- Replies:
- Re: Sequencer Preprocessor Build Rules Andrew Johnson
- References:
- Sequencer Preprocessor Build Rules Andrew Johnson
- Navigate by Date:
- Prev:
driver support for SIS3302 and SIS3305 Hu, Yong
- Next:
Re: asyn connection management with asynPortDriver Euan.Troup
- Index:
1994
1995
1996
1997
1998
1999
2000
2001
2002
2003
2004
2005
2006
2007
2008
2009
2010
<2011>
2012
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
- Navigate by Thread:
- Prev:
Sequencer Preprocessor Build Rules Andrew Johnson
- Next:
Re: Sequencer Preprocessor Build Rules Andrew Johnson
- Index:
1994
1995
1996
1997
1998
1999
2000
2001
2002
2003
2004
2005
2006
2007
2008
2009
2010
<2011>
2012
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
|