So many one liners, so little to say. I updated the site with the following changes:
- the "code" header now points to the machina page
- added "simulation file-system" project
- implemented an "auto" comment color script.. sorta.
Well; at least, the comments in all of the code I uploaded today are colored. As long as they are C-style. Anyway, I am a little worried/groggy/tired right now. A little more than 3 hours ago, I submitted the cs492 filesystem project to Ye Wu, who apparently had more than one email address. To make a long story short (and I have still not notified jerm about this) I forgot to include my lengthy readme and demo.txt in the tarball. Ah shit. I repacked it and sent it to Ye Wu like 30 minutes ago, but he seemed pretty adamant that all homework be in by midnight (the deadline.. dum dum dum). Either way, I hope he can see (you know, rego'nize) that 1. the modified timestamp on my source files in the repacked tarball are still on the 19th 2. that they have not changed filesize from the version I send in the previous mail 3. that I am the same person as the one sending that previous mail and 4. that theres no way in hell he shouldn't use the readme and demo.txt (files that only HE wanted to make grading easier) to grade the project. But there have been some instances of stupidity far worse than I can imagine as far as graders at Stevens go, and not only that, but wanting him to use it is really like asking him for a favor, but you'd do it for me, right man?
Anyway, I'm a little bummed that the project was not handed in entirely at the specified due-time, but I am content with letting my worries dangle on a thin thread suspended from the clutches of Ye Wu.
I found out today, after doing some lengthy code merges with Jerm, that our philosophies of capitalization largely differ. You see, mine is right, and his is retarded. Allow me to explain. Jerm will under no condition capitalize propper names, places, or beginings of sentences within his paragraphs, making following along difficult when you come to some sort of stop punctualization. Its impossible to find your place again, and you have to go and read back through all of the crap you had just read. That's just not my bag. Sure, I might not spell check whatever I'm putting up here, but that's because I don't care. But to care about appearance so much that you forgo capitals AND readability for the sake of some style that isn't even stylish.. thats just low. ON the other hand, while we're near it, coding presents an entirely new philosophy. Every single function in standard C (that anyone uses at least) is in lower case. When I go to code a function that will have a name consisting of two words, I do the manly thing and _ them together. That's right, thats what men do. Pansies, who use java and the like, prefer to capitalize. OK assholes, lets run a little test. What's more readable?:
ThoseWhoCapitalizeTheirCodeToDelimitSomeWordsInFunctionCallsAndVariablesCanKissMyAss.
those_who_use_underscores_and_lower_case_letters_are_hewn_from_greater_things.
If you picked the first one, go code in java where your compiled block of shite will run slower than some interpreter implementations of objective ML. If you picked the second one, well, welcome to the club of people who fuss over stupid things such as these. (As defined earlier by cmacgreg, #DEFINE's are a special case and deserve to be, well, special)
Either way, knowing this intimate knowledge, and the fact that I am not a big fan of the "tab", it should be fairly simple to pick my code out from the stuff Jerm wrote. His would be the stuff dissapearing into the right half of the screen. I'm too lazy to un-pre it. I'm also too tired to do anything but go to sleep. Peace.

public domain
comments