Professionals
If you look at most of the examples, the generic is used. But you may do as you say. But I will bet when you get to coding with the big boys, you will be using the "model". I am not sure at what level you are teaching for. I know that it saves me much trouble when I move between chips. Boost C has an even more generic one where you include system.h and it finds the right one based on the target platform.
If you are teaching at University level, I would suggest that using the generic creates the habits that will move forward.
Micro cpus like Pics create an interesting swimming pool of folks.
- Electronic hardware geeks who really don't know programming
- Software geeks who really don't know electronics
- And a few of us who know both sides (maybe one better than the other)
When I was in college, the EE folks did transistors, resistors, etc.
The Computer Science folks did programming
and the two really didn't meet except for when the EE folks had to take the programming course taught by crotchety old computer EE prof. They hated it. The CS folks ate it up. Was on a DEC PDP-11. Most modern PICs could outrun it today easily.
Times change. My brother who is an EE (same school, 11 years later) is more of a programmer than an EE. He designs stuff, but spends more time writting code.
But the issue is to come up with some good guide lines. Maybe for lesson 1 you are right. But at some point (maybe lesson 3 or so) the code has to be better.
All in Fun