It should not be a problem.

If you save a filter, you can find it in the URL. It is the requestID at the end.

Now with pictures instead of placeholders!

For this I defer to Darth Vader: http://www.youtube.com/watch?v=WWaLxFIVX1s

I think I'm going to end up going with Git. One thing which I hadn't thought of, is the fact that it might be a little easier now that I'm a Perforce Novice. As far as the repo on localhost goes, I have almost no confidence in being able to keep a computer on and accessible all the time. There now will be one other person with me for art and design, so I don't think I want to shoulder the responsibility.

Always insightful, Mitch!

Does that mean you believe goto is one of the most useful C paradigms?

No way! My for loops look like this:

for (int integerUsedForCountingIterationsOfAForLoop = 0; integerUsedForCountingIterationsOfAForLoop < 10; ++integerUsedForCountingIterationsOfAForLoop) {}

(Okay, maybe you got me there.)

You know, there are cases where the try / catch block is viable, but as normal program flow, I simply can't do it. It's dirty.

Now in some server-side application, perhaps you've no good reason to go down in flames simply because some library through an exception trying to convert 1/0 to an integer. You determine if it's severe, handle it gracefully (logging, email alert, message to the user), and move on. It just shouldn't be par for the course. Routinely ignoring all exceptions is a great way to rack up that technical debt.

Absolutely! We all know what they say about the word ASSUME. I'm also a fan of grabbing the original programmer to make sure a call or assumption about a system is correct as well! No reason to waste hours diving into some code when the initial response to passing null is horrible for a particular parameter and the calling code needs to be corrected!

Mitch, you should know I call it RTTI because of C++! The only thing is that I\'ve been scared silly of RTTI in games by people for performance reasons and in Obj-C, it\'s a pointer comparison for some of the operations due to the way they nest the Class member in classes.