Not that Microsoft is _always_ bad (just usually =) I've been dealing with converting a project from MS-SQL to Oracle at work for the past few weeks (or more accurately, adding code in parallel so that the user has the option of using either.) It's rather painful some of the stupid things Oracle does, or maybe it just seems that way because i started out on MS-SQL. But still, it seems entirely natural that it ought to be possible to do a search inside a procedure that returns zero results. MS-SQL handles this just fine, you get a null result back and as long as you remember to check the results before trying to use them everything is fine. Oracle on the other hand insists on throwing an error if a search in a procedure doesn't return any rows, which not only seems stupid, but handling exceptions in Oracle is a lot more painful than just checking for a null value in MS-SQL.
But lest i think too fondly of Microsoft, this new project has also involved learning to use C#. It seems pretty similar to C++ in a lot of respect, though there are some annoying bits of trivia. However the most trivial thing that has been bothering me the most is that MS Visual Studio insists that in C# projects breakpoints _always_ have to be highlighted. There's a even specific setting in the generic debugging options menu to turn highlighted breakpoints on and off, which works in C++ projects but gets ignored in C# projects =P
But aaaaanyways, when i checked