saturn return to sender

I have a sudden and terrible longing for pumpkin pie.

The fact that your phone can play mp3s as the ring tone is nifty and all, but now whenever I happen to hear Everything But the Girl’s “Flipside” I think my phone is ringing and must suppress the urge to jump up and get it.

I used to like that song. Hrm.

this is neither here nor there, and i intend to respond to comments in the previous post soon. but i have no one to share this with, so i’m going to blog it. though it’s not like anyone who reads this will care, either.

i am experiencing some extremely uncool behavior with Apple’s XCode. i have a library statically linked in my project. i have the code for the library. at some point i added some logging code in the library. i now want to remove that code. it’s expensive and annoying.

okay, so i pulled the call and re-built. the logging still happens.

i have built clean five times, i have pulled references to the library and put them back in, i’ve turned off ZeroLink. i have deleted the library object file and rebuilt. i have deleted all my main project products and re-built. i have deleted the file with the code to call the log routine. the function called “log” no longer exists. i can break the library build (by writing the syntactically anomalous but viscerally satisfying what the fuck???? on the first line of a function call. when i un-break it, the behavior returns. i have restarted XCode. i have done everything short of re-assembling the projects from scratch or throwing my computer out a window.

THE LOGGING CODE WILL NOT GO AWAY.

if i set a breakpoint on NSLog, it hits. the stack trace points to a place in the source where the call to “log()” USED TO BE. for the frame containing the “log()” function itself it shows absolutely nothing. BUT THEN SOMEONE IS CALLING NSLOG, ANYWAY.

this is not cool. i am going to get a beer.

A fellow I met during my touch-and-go work with the Integral Institute recently spent several weeks on a vipassana retreat. He has a blog, and he has started to write about those weeks.

This article is an attempt at putting words to what I’ve experienced during the course of those six weeks, and will in many ways be quite pointless. The reason I say that is because when one reflects on one’s experience and tries to share some essence of that with another there are at least two assumptions that one makes, which in the Therevadin tradition of Buddhism are not assumed, and are in fact challenged. One is that experience is happening to someone, a self, a person, a being, and the other is that these experiences somehow matter in some grand way.

Good stuff.

… In a well-the-two-things-seem-related-to-me thought … I got a history paper back today. (more…)