Clang - Spurious Errors Fixed with Undo
Clang - Spurious Errors Fixed with Undo
- Subject: Clang - Spurious Errors Fixed with Undo
- From: Brian Barnes <email@hidden>
- Date: Tue, 8 Sep 2009 11:29:31 -0400
I'm trying to track down a number of clang errors, but they mysterious
get fixed through undos. For example, I had a header file with a
number of defines like this:
#define xxx abc\
def\
hij\
etc. Maybe about 100 lines of this, in different defines. About
halfway down, I get "backslash and newline separated by space" which
is repeated for all other lines past that. I retyped the line, and it
works. Now the odd part -- I "undo" the typing to try to determine
the difference -- and it still works!
Does undo fix line endings, or remove control characters? I lost the
change I was tracking there, so I can't figure it out to submit a bug
report! I suspect this might be a problem with changing line endings
or control characters in the file, but now I can't get a handle
because it's "fixed"! So, there's some information for you, it's the
best I can do (sorry).
Also, when I have gotten things to compile, my code always ends up
crashing in OS X -- usually in a UI routine -- my code's still in
carbon (yes, I know) so that might be a factor, or it's an unforeseen
problem I got away with in gcc. Also tracking this, and I also get
spurious "symbol not found" which I haven't gotten a handle on yet,
either.
I'm wondering -- should I not use this for carbon?
[>] Brian
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden