I've always seen and hated those weird macros that preceded functions of header files. Why couldn't they be clean and simple? I hated them because I didn't know much about them, they seemed arbitrary, prone to error, non-standard, no way of knowing the real motivation behind. 

Not anymore. Today I had to create an intermediary DLL between two different object file formats and I had to go down to the level of dirty and hacky in the quest to make it work. And I stumbled upon this awesome page that has the "ultimate header file" template. I discovered half the things there myself, but it nailed the coffin of problems for me. 

Here are the problems that I had to tackle in general:

hahaha I might not have an iPhone but I have the simulator. I'll edit this and add a screenshot:)

(attached is the screenshot)

Here we go. I formatted my laptop hard drive, wiping away both Windows and Gentoo Linux... It was a tough choice nevertheless, but I had to because (1) my reiserfs partition got corrupted and some config files at my home directory were unwriteable (creating all kinds of fun), (2) my windows partition was too small to do any development on, (3) with the advisor change, I stopped using my laptop at work. I also stopped using Linux at work and entered into the mighty world of Java and Windows, a very positive experience indeed. 

Hi Ali,
Thank you for havin' me in your homepage.we were in a small town near Wien which have a small sea, it's a nice place about 45 min. from wien, we were there for weekend so didn't got the chance to answer your E-mail.The other letters were in the envelope, thanks again.
So that was your fault, had headach 'cause of the ringings in my ears, please don't do me that again.
We will be goin' to States at the end of September i can't say if we're gonna stay(I don't think so),if i see that i'm good prepared for the test, i'm gonna make it if not, November.
So u have enough time for visit(check your Palm!)
I will send u one more pic with this.
Say hi to all,
Renato

Hi Ali,
I've got the package, thanks a lot.It was open but the DVD's were still in it so i think someone wanted to check it!!good to hear that u don't have much to do so u can Dictate my dismissal letters.
Don't forget about visiting us in Vienna.as i told u check Germanwings or Ryanair.will be glad to havin' u here.
Kiss Jonnathan.
Renato

Bir haftadir 21 gunluk vatani gorevimi yapiyorum, merak eden herkese selamlar, ben iyiyim.

I've been doing my military service for a week now. I'm OK in case you were wondering.

Right now, the binarySearch for collisions stop when the distance for the first contact is within the collision tolerance. For high tolerance values this seems to be ok, but high tolerance creates less accurate simulations.

When the tolerance is low, the while loop in Simulation::binarySearch() actually gets executed and the simulation ends up stepping lower than the real step size. This is easily verified by doing sim->getCollisionDetection ()->setTolerance (0.0001) in CollisionModel.cpp. As the bodies start hitting the ground, the actual timestep varies as can be seen by the time display on the render window. I think this is bad, since most applications would expect the simulation to have the same step size everytime it is stepped. Attached is a patch that forces Simulation::timeStep() not to return till the expected timestep is reached.

http://www.impulse-based.de/phpBB2/viewtopic.php?p=151

Oh boy. I saw this comment rant when I surfed over to the news about KDE looking for summer of code dudes. While I agree 100% with most of the comments he makes there, I'm a Linux user by choice - such a paradox...

It's not necessarily that Windows is far more superior than Linux, it's just that simple and intuitive tasks get done in Windows easier than they are in Linux and things in Windows just work without problems most often than in Linux. On the contrary, Linux shines when you are obsessive about how you want things done, therefore it's occasionally more fun.
You want to do NAT in Windows? You buy Wingate and you are done. You can see all the connections live on the Window and you have a lot of control over what happens with it, very discrete from anything else in the system. In Linux you have to learn what iptables is, how you sort of indirectly use its internal structure for NATing, etc.

(a) If you have time to do all that, great. Now you are an iptables guru and it'll be very helpful for many other things you will want to do at some point in the future. This definitely is a plus over a simple solution that works and does just what you want. (b) BUT, if you DO want a simple solution that works and does just what you want, your best bet is to find a howto and copy and paste a bunch of commands that you don't have much idea about. In such a case you'll have much less control over the whole thing, and when it breaks you'll spend much more time on it since you'll most likely have to revert to (a). This is definitely bad for the person that wants simplicity.

This is not exactly a development contribution in terms of code, it's more like an idea. Nevertheless, I wanted to note that I was helpful to someone doing some development by leading them to the right direction on the ode-users mailing list.

Curlpp had a recent release that acknowledged me by name for submitting a patch.