Welcome to the blog of Can Sar, a Stanford CS major. This blog is made up of my thoughts on Computer Science and the computer industry, as well as ever exciting tales from my life.
I just spent 3 hours trying to figure out why I was getting compile errors in a file called /usr/include/sys/isa_defs.h that I had NEVER heard of before. It turned out it was caused by me accidentally putting the word www in the first line of a completely unrelated .h file, while trying to open a website (I selected the wrong window). All compile time errors are now fixed again, and I am working on getting networked file reading working, while chilling to the sounds of Faithless.
Posted by Can Sar at July 16, 2004 08:06 AM to category Computer Science | TrackBackI did that all the time with my Music 220C project; since it lasted all quarter I eventually put comments at the top of every file (//) and then every compile had Visual Studio call a python script that threw a warning if there was something else on the first line.
I made similar mistakes in 140, and I know Tristan did too - they take so much time to fix. Maybe you should make your OS only run one process at a time :)
Posted by Travis on July 16, 2004 06:14 PMi've been doing that all the time too, except im not as resourceful as travis; i pretty much just assume this is the case if i ever get compile-time errors nowadays.
Posted by es on July 18, 2004 12:09 AM