Re: xcode chokes on #include<somefile.lxx>
Re: xcode chokes on #include<somefile.lxx>
- Subject: Re: xcode chokes on #include<somefile.lxx>
- From: jean-françois gauthier <email@hidden>
- Date: Tue, 20 Apr 2004 08:03:50 -0400
does anybody have an idea as to *why* the #include implementation tries
to decide what really is a header? whats the purpose of having
#include "a.h" be smarter than #include "a.c", is it a feature? it
seems #include "a.c" limits itself to the folder containing the current
translation unit, simply ignoring source tree and header search path
settings. this is causing me grief since i have a lot of legacy code
that includes .cpps.
jean-frangois
Le 20 avr. 2004, ` 1:02, email@hidden a icrit :
I wonder if Xcode is getting confused since it sees .lxx as a file that
needs to be processed by lex/yacc. Please file a bug, so we can figure
out what is going on.
Scott
_______________________________________________
xcode-users mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/xcode-users
Do not post admin requests to the list. They will be ignored.