been a while, huh? you don't have to lie and say that you missed me.
so i just decided to bite the bullet and try to use this dang c++ contraption that i've heard so much about (after running across a big beautiful 3rd edition of "N– R–", on which one of the authors is the esteemed Dr. W. P., whom I'm pretty sure is the one I found on wikipedia who looks exactly like my forebears. but that's neither here nor there).
thing is, it's apparently unstraightforward to work in c++ on spit and string, the way one can do with python or whatever. fucking compilation...
so you need either the ms visual studio or xcode. i'm on my pretty little air, so i'm using xcode. to someone unused to it, xcode blows. not a good way to learn this....
##update on cpp:
got xcode to work- a case of clicking on the wrong thing when there was no obvious way of knowing that there's a right thing. in my opinion, a classic case of overdesigning a tool which then becomes the standard because people are afraid of doing things simply, over the command line. on that note, i soon learned that compiling from the command line is a snap with the g++ compiler:
(my stupid little program is fail.cpp, which takes input from the user and then insults them)
/Users/~/cpp_failures
==> g++ -o failure fail.cpp
/Users/~/cpp_failures
==> ./failure
write it, bitch: wicked
fuck you, wicked
this is C++ talking.
i do not anticipate using xcode again for cpp, unless i get into software development by some strange and unforeseeable twist of fate. my needs simply aren't that complicated.
##
otherwise have been writing many papers. also doing a journal club talk. also preparing for committee meetings and general exams etc... oh and also c tells me that i need to repeat an experiment doublefast which i don't have seeds for... so it can make the paper go to nature, which will maybe piss off su?
so i'm feeling a little tense, is what you could say.
