Personally I think it's best to code in your own style, whatever the language. My current project is in DBPro and C++, and the actual game logic is practically the same. C++ can be as procedural as you like, DBPro can be as object orientated as you like.
When it comes to game programming, you really are better off just getting stuck in, because experience is the most important thing. Game programming experience is transferrable, because it's more about technique than syntax. If you code a particle engine for example, in DBPro, then the next time you code one it'll be leaner and better, and if you then go onto making a C++ particle engine, then you'd find yourself using the same techniques. I find that the biggest difference is in rendering engines, well any 'engine' component - you have to do more legwork with C++, but that also affords you more control over things.
If you want to make games and have never done so, pick up DBPro and learn that, it covers everything you need to know, and if you start to outgrow it, theres always DGDK and other C++ engines out there.
Health, Ammo, and bacon and eggs!
