I have been programming for about 10 years: 7 years C++, 3 years MFC, 2 JSP/Servlets, and the last year .NET (since there was some overlap the total won't add up).
The problem is now that I am looking for a new job, I don't know what the latest thing is in C++ AND Java AND .NET AND MFC and somehow at interviews I am expected to KNOW everything about these topics because I have them listed on my resume.
Any suggestions?
I expect that an Experienced Developer has learned from their experience, and not just spent time writing the same code over and over. You're not expected to know everything, but you're expected to have a degree of wisdom which comes from years of experience.
Compared to other languages, even C++ doesn't move very quickly. However if you're planning to list 7 years of C++ on a resume, I would expect you to know a lot, as well as be up to date and familiar with the latest trends (might I suggest Boost, C++1x and various popular C++ open source libraries), and have a wealth of experience with templates, advanced C++-style OO, debugging, cross platform and performance awareness.
If you're looking to get "up to date", the trends I listed earlier, plus the usual mix of a graphical toolkit (perhaps Qt), a scripting language for your platform of choice, and the latest batch of build systems (VS2k8, CMake, etc.).
Just because you are asked something, doesn't mean you are expected to know the answer instanteously. Some of the questions may be designed to see whether you can say "I don't know" or if you are the type to take a guess and blindly hold on to it for dear life. Other times there may be an expectation that you have had this situation or that and how well do you remember what was done in those situations.
Just to provide some more background, I've been doing web development now for 12 years and have had quite a few changes in terms of what I use including 6 years of ASP, 7 years of .Net ranging from 1.0 to 3.5, and a couple of years using C++ in various forms as some of that was using COM objects and some was using VC++ 6.0 back before my ASP days. There are times where even now I will have some legacy ASP issue to work through so having that experience is handy, but I'm not sure I'd want to try to go off and write an ASP interpreter or C# compiler.