ober, I don't do professional web-developing, but have done a little bit of raw html and I've been meaning to get a book on css. As for IE, yes, I've heard it said often that IE lets illegal html go, but it's really Microsoft's choice, I think. They've probably analysed this issue, found the majority of users not web developers like the browser to guess the best layout, and then built the software. Or they built the software and then found fixing it to be too costly. Of course this situation puts the web developers at a disadvantage---kind of like a compiler that guesses variable names. But Microsoft probably thinks a good developer would test a page using the three main browsers and maybe a few rare ones such as Konquer.
okinrus, you need to do some reading and some web development to understand what we're talking about here. IE is the bane of any true web developer and if you start developing yourself, you'll find that you develop with Opera or FF (Opera is my choice), and then you make corrections for IE.... not the other way around. IE is a piece of tolerant garbage IMO, and unfortunately, I think they're at a point where they won't ever be able to fix the mess they've got themselves into. Fixing the browser to support the current standard would mean that they'd break probably 60% of the websites on the net. I'd love to see that day, but unfortunately for us, I don't think MS would do that because everyone would stop using their stuff.
xrath, fflush stdin is undefined by the C/C++ stdandards; any compiler is free to define this behavior and remain standard. But personally, I think the best behavior would be for the compiler to mark it as an error or warning. I don't think microsoft or gcc does this.
The same applies for C/C++. If you write good clean and portable code, you can be sure it'll almost work on any platform. If you try stunts like fflush(stdin); you'll get a unwanted operation, but any MS compiler will flush stdin, because it doesn't conform to the standards.