cheerfuland then, passed out. I mean I lost consciousness before I could even put my feet up. one minute I was reading and the next minute I was having some weird dream and then waking up with my glasses in my hand (I took them off?) and my chin buried deep in my chest. feet flat on the floor. four hours had passed.
then I got up to go to the bathroom, was playing a game of solitaire on my cellphone, blinked, and suddenly the game said I'd been playing for an hour. I looked at my watch. an hour had passed during that blink. oddly, my ass was not numb. I got off the can and went to bed.
I'm going to be a real riot when I'm old.
now I'm going to study Objective-C until I pass out again. main reason I'm still studying it is that this particular book is so far the best book on Object-Oriented Programming that I've tried to use. all the others teach you expressions and loops and all of these procedural things before introducing this mysterious and tricky entity called the "class" and its "methods" and then give you this weird syntax on how to invoke the
this one was just like, look, here's a class, here's how you make an object out of it, and from now on were going to confine most of our programming to writing methods and then calling them instead of creating dozens of little procedural programs that don't have anything to do with each other.
if you know what I'm talking about you might see how this is a much much better approach. if you don't you don't care and probably never will but I'll just say I'm happy and it's useful so I'm going to try actually to finish this book because it is working so much better than all the others.
then it's back to python and reading the manuscript that I'm "editing" when work begins in, oh, 24 hours or so. Objective-C is for fun. :)
