Re: xcode 2.2 creates 'virtually corrupt source files'
Re: xcode 2.2 creates 'virtually corrupt source files'
- Subject: Re: xcode 2.2 creates 'virtually corrupt source files'
- From: Stefan Werner <email@hidden>
- Date: Tue, 13 Dec 2005 22:43:14 +0100
Hi,
On Dec 13, 2005, at 10:26 PM, email@hidden wrote:
Message: 2
Date: Tue, 13 Dec 2005 12:35:56 -0800
From: Mike Halpin <email@hidden>
Subject: xcode 2.2 creates 'virtually corrupt source files'
Anyone seen this behavior, or know how to make it stop?
I've seen it, way to often.
Since I did a clean checkout to an external drive, and started
building there, found that I get compile time errors which appear to
be the result of random garbage, or sometimes a string of '?' in
place of some of my code in one or more source files.
I had that not only in my source code files but it also happened that
Xcode project files ended up like that...
I was getting ready to trash the latest bad file and then update from
cvs to get a clean copy, but decided to open it one more time to make
sure I was choosing the problem file.
...which is what I did then. 'cvs update -C .', go brew coffee, calm
down and try to not be angry about all the lost work (is there any
way to make the Xcode editor to create backup copies of any modified
file, btw?) and curse FileVault, which is what I blamed for the data
loss (it behaves weird once I have less than 1GB free space).
Double clicked on it and it
opened in Code Warrior (no surprise there, I have recently ported
from codewarrior, and all my sources are still tied to it as their
creator), BUT......
THE FILE WHEN VIEWED IN CODE WARRIOR WAS FINE!!!!!!!!
You mean all my files were not lost? ARRRGGGHHH!!
-Stefan
_______________________________________________
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