Finals next week

[merlinofchaos]

2nd semester's almost over!

And then I take a summer C++ class for 8 weeks.

I expect it will be so ludicrously easy that my worst trouble might be finding it so boring I don't do all the work. On the other hand, I haven't done any actual coding for a long time, so hopefully the projects will be just interesting enough that I want to do them just to write something again.

Comments

[callicrates.livejournal.com]

There's a third possibility: go way beyond what the professor expects and have fun with it. Use templates. Use abstract classes. Avoid multiple inheritance if possible. Use the STL and namespaces and operator overloading.

I still boggle at the fact that the template stuff in C++ is Turing-complete. This means that (in theory) you can perform any computation at compile time. A friend of mine gave his class the exercise of computing prime numbers and printing them out in the compiler warning messages.

I will not be held responsible if your professor falls over when trying to grade your assignments, but you could certainly have fun.

[merlinofchaos]

There's a third possibility: go way beyond what the professor expects and have fun with it. Use templates. Use abstract classes. Avoid multiple inheritance if possible. Use the STL and namespaces and operator overloading.

Multiple inheritance is evil. I rarely use it anyway, though sometimes it's unavoidable.

I admit that I rarely use templates, because they are compiler magic and don't always behave quite the way I expect them too.

Abstract classes, on the other hand, are a real backbone in my C++ programming. It makes things come out much cleaner, IMO.