You know, this makes me think of the movie Space Cowboys. Will object oriented coders be able to grasp non-orientated language concepts? It's not just a matter of learning a new syntax. It's learning an entire new (to them) methodology. (That was a major issue in the movie - people steeped in new techniques didn't grasp the old technolgy.)
For me it was the other way around. It took me about three months of staring at screens and trying to write code, reading references, etc., before I got the hang of object oriented. My challenge was creating smart applications in Office suite using Visual Basic, particularly Access. I had previously created interfaces in Rbase, but I couldn't get the hang of how to initiate execution in Visual Basic.
But once I figured that out, I realized that all of the linear stuff still applied during code execution. I could still create functions and subroutines as I normally did. And I figured that I was writing some pretty good routines using my linear programming training.
My hang up then, and still this day, is that I couldn't figure out where in the object model I was. For example, when I'm doing some tasks, I don't understand why I need to create an application object for the application I'm inside of. It would seem to me that if the application is open, and I'm coding inside that application, then there must parent application object that exists and that I can reference.
In linear, that realm doesn't exisit. You define your variables, you set values, and that's it. Or you create a screen, where your defined variables populate specific areas on the screen. And you read from or write to your data file as needed.