Other then citing one study for pascal,
it wasn't on pascal it was on beginning with OOP vs. procedural programming in universities.
What exactly are you advocating anyway, learning procedural programming first, or learning a low level language like C/C++ first
i advocate learning procedural programming first.
Other then that I don’t think that learning to do something in a *very* old and *very* ineffective way first helps you in any way
it's not very old. it is how your computer does it. today.
This API is very complex, cryptically-named, and for the most part with a linear (non-OOP or hierarchal ) in C and C++, but is very intuitive and well-documented in C#
that problem is specific to the windows API ? (counter example OpenGL)
And if you check the US Department of Labors 2004 Statistics for "Average Anual Salaries in Software Development" you will find that Object-oriented programmer make $68K (the highest of all soft-dev jobs listed) while non-OOP programmers make $59K
what exactly does that have to do with wether it is better to learn procedural and build OOP on that or the other way round ? i told you before, i'm not questioning OOP. why do you constantly keep attacking me on that ?
You said that because people learned java and didn’t understand their computer that they should have learned procedural first
i based that observation on operating system courses we had to take in later semesters. you could easily see that they had difficulties in understanding what happend because they had little understanding of what the computer actually did so far.
you know... i have the feeling that all that you are concerned about is application writing. i even agree with you that when you are only dealing with business world programming and writing apps in that area you are better of with never careing too much about low level things besides how you can write efficent code for your CLR. but there are other things to do than that. people do write code for the linux kernel and people do design low level network logic or programm AI into robot (or write high performance code ala Nick's swshader/softwire). about all research projects, my university is involved in, require skills in object oriented programming as much as writing specfic assembler code or work at lower levels that don't permit the luxury of object orientation. so you have two sides that both need to be covered and the question that remains is how you should teach about both of them. we have different opinions on that and that's ok
ps : i'm really sorry that i couldn't find an online verison of that study. i couldn't even find the website of the us didactic boards (do they exist ? i don't know... mike's pawnshop has a website... so you'd expect them to have one :) ). anyway...