Here's the rub, should we teach the function library approach, or an OOP class approach? I know there is a place for procedural, but it's not something generally looked for in a programmer's skillset these days (open source apps aside). Touching on function libs is just one step away from OOP, and failing to bridge that gap early leads to the situation in the above quote. I've seen it dozens of times - if you focus on procedural readers are taken down a path which can be very difficult to escape from. Contrary to some people's perception (not targeting anyone here) OOP is not an easy to understand topic for everyone - it can actually be very difficult. It takes a small epiphany to suddenly "get" it. And even then there is a massive amount of recommended practice to figure out. Starting small, and presenting those practices (even if they are not formally identified) would get a reader used to the ideas to the point they expect to see them.I mentioned it only because it is hard to become adjusted to OOP after seeing so much procedural.
I won't be mentioning this again, because it's directing focus away from organising/brainstorming the book. It may be something to discuss at some stage down the line when the book is at a slightly more advanced stage in planning.